Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 763b30662166663262ff937e8139463ce0079b3866e185664f87277ba63901fa

Tx prefix hash: 665db9513b69206f4b37011f513cf80c1cd246a403d5f54e1858a6836c45e3b9
Tx public key: 5c677e9fd12bb65c2b1b9c0ab62655f6e7f2155a8f862a2589ce5417f6282b79
Timestamp: 1708151057 Timestamp [UCT]: 2024-02-17 06:24:17 Age [y:d:h:m:s]: 01:040:11:15:38
Block: 959314 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 289959 RingCT/type: yes/0
Extra: 015c677e9fd12bb65c2b1b9c0ab62655f6e7f2155a8f862a2589ce5417f6282b7902110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bff6bdad6fd59cdde1b230fa36e7ce10a5194c22b4861d537dcf74b2f1d94ed0 0.600000000000 1418849 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": 959324, "vin": [ { "gen": { "height": 959314 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bff6bdad6fd59cdde1b230fa36e7ce10a5194c22b4861d537dcf74b2f1d94ed0" } } ], "extra": [ 1, 92, 103, 126, 159, 209, 43, 182, 92, 43, 27, 156, 10, 182, 38, 85, 246, 231, 242, 21, 90, 143, 134, 42, 37, 137, 206, 84, 23, 246, 40, 43, 121, 2, 17, 0, 0, 0, 4, 82, 212, 126, 148, 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