Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 153266d35fe2f3088cf343f4d102febf1d86d9f2418f7f80e5e2ef4fc5150661

Tx prefix hash: d497c195c1990cd59dc45129e1383348f1ee400958ed8b511ea83442e5b69783
Tx public key: e85727f6dc58d0fc0d5f1bb1f958ea931dce698868cad17ccfbf09c005ac1e08
Timestamp: 1734658566 Timestamp [UCT]: 2024-12-20 01:36:06 Age [y:d:h:m:s]: 00:089:20:42:26
Block: 1178988 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 64010 RingCT/type: yes/0
Extra: 01e85727f6dc58d0fc0d5f1bb1f958ea931dce698868cad17ccfbf09c005ac1e08021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8ec3eafddca94882c0901a97939baa7f5d34c8a8bee1b401f35d76c81143c04d 0.600000000000 1665379 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": 1178998, "vin": [ { "gen": { "height": 1178988 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8ec3eafddca94882c0901a97939baa7f5d34c8a8bee1b401f35d76c81143c04d" } } ], "extra": [ 1, 232, 87, 39, 246, 220, 88, 208, 252, 13, 95, 27, 177, 249, 88, 234, 147, 29, 206, 105, 136, 104, 202, 209, 124, 207, 191, 9, 192, 5, 172, 30, 8, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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