Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ec3e9a46174359566bd889a51c3596c0306152d8ea704d5ab69836b225fe7739

Tx prefix hash: 981bdf7fde796655b0d98cb426dc3ef990c211bf9fe275131f7363ccbd95655e
Tx public key: fee709ae9d41ccb5a894e363bb272c41973d2dc5ba82a3378e2ab0ddc43f6120
Timestamp: 1577564845 Timestamp [UCT]: 2019-12-28 20:27:25 Age [y:d:h:m:s]: 04:327:23:48:40
Block: 33813 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1123533 RingCT/type: yes/0
Extra: 01fee709ae9d41ccb5a894e363bb272c41973d2dc5ba82a3378e2ab0ddc43f61200211000000034ac5aa02000000000000000000

1 output(s) for total of 474.219029051000 dcy

stealth address amount amount idx
00: be0b7676d29ccefb3b1bb732c6563a698eede7e807aaaa24bf68e5a95dd8f3c8 474.219029051000 56741 of 0

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": 33823, "vin": [ { "gen": { "height": 33813 } } ], "vout": [ { "amount": 474219029051, "target": { "key": "be0b7676d29ccefb3b1bb732c6563a698eede7e807aaaa24bf68e5a95dd8f3c8" } } ], "extra": [ 1, 254, 231, 9, 174, 157, 65, 204, 181, 168, 148, 227, 99, 187, 39, 44, 65, 151, 61, 45, 197, 186, 130, 163, 55, 142, 42, 176, 221, 196, 63, 97, 32, 2, 17, 0, 0, 0, 3, 74, 197, 170, 2, 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