Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f1a776f5922f8e0b8f3cf1a05c473afcce27098d9fa0be73e6fc90e4355224b2

Tx prefix hash: d3edf1396a14708739afaef0d608b53e4eda2366cc9163d3481a5d359d11c578
Tx public key: 62f917e5eb75e94d4363a1132b78be9c5d8f3d5efed358e8739d49ad49443d36
Timestamp: 1672761603 Timestamp [UCT]: 2023-01-03 16:00:03 Age [y:d:h:m:s]: 02:008:14:22:40
Block: 666787 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 528066 RingCT/type: yes/0
Extra: 0162f917e5eb75e94d4363a1132b78be9c5d8f3d5efed358e8739d49ad49443d3602110000000433af99f4000000000000000000

1 output(s) for total of 3.790162536000 dcy

stealth address amount amount idx
00: 885629e0470128f1ea986ea9fb7ea79bf7909a93ff1adc133e8382864e841f74 3.790162536000 1107928 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": 666797, "vin": [ { "gen": { "height": 666787 } } ], "vout": [ { "amount": 3790162536, "target": { "key": "885629e0470128f1ea986ea9fb7ea79bf7909a93ff1adc133e8382864e841f74" } } ], "extra": [ 1, 98, 249, 23, 229, 235, 117, 233, 77, 67, 99, 161, 19, 43, 120, 190, 156, 93, 143, 61, 94, 254, 211, 88, 232, 115, 157, 73, 173, 73, 68, 61, 54, 2, 17, 0, 0, 0, 4, 51, 175, 153, 244, 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