Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5701ceeeb935be53ddaa5a5cda6a186f6e2efb8990d1a6a5e4e1ff2632915622

Tx prefix hash: 7a246d40a523b282bce3dd387ee86f780615f926436e16ebcef7339760fb3084
Tx public key: f915feb151542b1fd908d2984bf22d83f6045a5e31f026f5d63e300465f52adf
Timestamp: 1734543371 Timestamp [UCT]: 2024-12-18 17:36:11 Age [y:d:h:m:s]: 01:003:08:29:07
Block: 1178041 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 260808 RingCT/type: yes/0
Extra: 01f915feb151542b1fd908d2984bf22d83f6045a5e31f026f5d63e300465f52adf0211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3c406a5ebb3a5d2f269661217196aa951ef3de366f2bf048422f83f3865e81a6 0.600000000000 1664424 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": 1178051, "vin": [ { "gen": { "height": 1178041 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3c406a5ebb3a5d2f269661217196aa951ef3de366f2bf048422f83f3865e81a6" } } ], "extra": [ 1, 249, 21, 254, 177, 81, 84, 43, 31, 217, 8, 210, 152, 75, 242, 45, 131, 246, 4, 90, 94, 49, 240, 38, 245, 214, 62, 48, 4, 101, 245, 42, 223, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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