Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 95c44840a595c155d59000ce0644e2882f6b7005bae4d9efba39d3878a12fabe

Tx prefix hash: 0ae4688513e7585936d3d317671866878c519a253b595604134dff540faf7b8d
Tx public key: 07e2fa9b069e1dc6fc00384de1194a53c9b7b0095d5d9a165fef1c1e19d13101
Timestamp: 1720827678 Timestamp [UCT]: 2024-07-12 23:41:18 Age [y:d:h:m:s]: 01:124:12:13:48
Block: 1064430 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 347496 RingCT/type: yes/0
Extra: 0107e2fa9b069e1dc6fc00384de1194a53c9b7b0095d5d9a165fef1c1e19d13101021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b0081f580c5f15e5a84c126e94bd457d27225eee38ea705265c15e55409e888d 0.600000000000 1534957 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": 1064440, "vin": [ { "gen": { "height": 1064430 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b0081f580c5f15e5a84c126e94bd457d27225eee38ea705265c15e55409e888d" } } ], "extra": [ 1, 7, 226, 250, 155, 6, 158, 29, 198, 252, 0, 56, 77, 225, 25, 74, 83, 201, 183, 176, 9, 93, 93, 154, 22, 95, 239, 28, 30, 25, 209, 49, 1, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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