Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: c5278794cd6ea8dd0225260c048379a12f35d2a3e75dbd55c5f079519f199ed2

Tx prefix hash: af2eb36a5a9def2277d07cea92920b0e35b05a5955cddf8c68ab8066e65a201d
Tx public key: 5d8d94ad9e63c5072b4f769d74ec540acfd440096693449a44caccfb78ee863d
Timestamp: 1709405034 Timestamp [UCT]: 2024-03-02 18:43:54 Age [y:d:h:m:s]: 01:032:11:43:10
Block: 969728 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 284218 RingCT/type: yes/0
Extra: 015d8d94ad9e63c5072b4f769d74ec540acfd440096693449a44caccfb78ee863d0211000000087a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 629ea636f5b69ec1b0f5e3eb6eee8b2f75bcd52aa2ad67aaa62eacd44370799d 0.600000000000 1429567 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 969738, "vin": [ { "gen": { "height": 969728 } } ], "vout": [ { "amount": 600000000, "target": { "key": "629ea636f5b69ec1b0f5e3eb6eee8b2f75bcd52aa2ad67aaa62eacd44370799d" } } ], "extra": [ 1, 93, 141, 148, 173, 158, 99, 197, 7, 43, 79, 118, 157, 116, 236, 84, 10, 207, 212, 64, 9, 102, 147, 68, 154, 68, 202, 204, 251, 120, 238, 134, 61, 2, 17, 0, 0, 0, 8, 122, 156, 244, 199, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8