Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f7d16f48d8bf77875f42a4f8ce559ee7d4f0fb810899dec35e7f88414f9c1436

Tx prefix hash: ab12c5306af98d4c700cd72c10658f0b847727313864eafb301e68c3e16f575c
Tx public key: 3620b4bcd6ab8dad12dd9ceb56dacd07f5a29878a0a60e8252911ea62f11e671
Timestamp: 1721477588 Timestamp [UCT]: 2024-07-20 12:13:08 Age [y:d:h:m:s]: 01:103:09:02:29
Block: 1069805 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 332383 RingCT/type: yes/0
Extra: 013620b4bcd6ab8dad12dd9ceb56dacd07f5a29878a0a60e8252911ea62f11e67102110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ab55cea2476a750c4cd8ec53cb9b0a4c9e44f1db5a7b78158bbb08d7a75102c2 0.600000000000 1541382 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": 1069815, "vin": [ { "gen": { "height": 1069805 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ab55cea2476a750c4cd8ec53cb9b0a4c9e44f1db5a7b78158bbb08d7a75102c2" } } ], "extra": [ 1, 54, 32, 180, 188, 214, 171, 141, 173, 18, 221, 156, 235, 86, 218, 205, 7, 245, 162, 152, 120, 160, 166, 14, 130, 82, 145, 30, 166, 47, 17, 230, 113, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 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