Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 61fee5a0e8f0113556b5929c2301b305fead87f16f1ccaddd2b41701cb9bf392

Tx prefix hash: 11e98ba8cc170776b55e0d6c922ccfdd0ca01b1ab4ee47f625603dc4bf145c01
Tx public key: 6871267af2cb62121a728bd1afdfa5287c3e0a4d68198933286c8ecfbb57059f
Timestamp: 1724321755 Timestamp [UCT]: 2024-08-22 10:15:55 Age [y:d:h:m:s]: 00:224:10:50:13
Block: 1093399 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 160260 RingCT/type: yes/0
Extra: 016871267af2cb62121a728bd1afdfa5287c3e0a4d68198933286c8ecfbb57059f02110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e329df4a4e03ee70b028a7df23f22c4b1731f91a198da6a4db2a7886792720a2 0.600000000000 1568334 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": 1093409, "vin": [ { "gen": { "height": 1093399 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e329df4a4e03ee70b028a7df23f22c4b1731f91a198da6a4db2a7886792720a2" } } ], "extra": [ 1, 104, 113, 38, 122, 242, 203, 98, 18, 26, 114, 139, 209, 175, 223, 165, 40, 124, 62, 10, 77, 104, 25, 137, 51, 40, 108, 142, 207, 187, 87, 5, 159, 2, 17, 0, 0, 0, 1, 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