Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6d01ea619bc40b14fb3f2ba8efb6fdf3c2380a2a39a5e8bfbd6458493fb8f0f8

Tx prefix hash: e1126084815763928af89ba1a2adb6cd7c8239da768f882464e295261d6071a8
Tx public key: 237429c1b401cf36e0ae57f863e6953ca1023f282eeff44f0b11cb3eb44bb288
Timestamp: 1715663405 Timestamp [UCT]: 2024-05-14 05:10:05 Age [y:d:h:m:s]: 00:336:06:48:37
Block: 1021603 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 240370 RingCT/type: yes/0
Extra: 01237429c1b401cf36e0ae57f863e6953ca1023f282eeff44f0b11cb3eb44bb2880211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 790cca18d3d2084f9fee3310b0b77a675c8556e0588a7b50c74106bbd95214d1 0.600000000000 1485972 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": 1021613, "vin": [ { "gen": { "height": 1021603 } } ], "vout": [ { "amount": 600000000, "target": { "key": "790cca18d3d2084f9fee3310b0b77a675c8556e0588a7b50c74106bbd95214d1" } } ], "extra": [ 1, 35, 116, 41, 193, 180, 1, 207, 54, 224, 174, 87, 248, 99, 230, 149, 60, 161, 2, 63, 40, 46, 239, 244, 79, 11, 17, 203, 62, 180, 75, 178, 136, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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