Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1b9d9e377b9ab7e6e61cdae98704f2cf96fa4b695432c1ae7858b982b64674b8

Tx prefix hash: 561f2c2d263651c0069561ed654fe1c171e79282fc48f4e5d2ca11b85ced3142
Tx public key: 8e7dda9f0937d8830e8eb78412ed6857c8c4474413d43eef71c96f0bb804f9e3
Timestamp: 1646926901 Timestamp [UCT]: 2022-03-10 15:41:41 Age [y:d:h:m:s]: 02:319:17:45:53
Block: 455500 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 747973 RingCT/type: yes/0
Extra: 018e7dda9f0937d8830e8eb78412ed6857c8c4474413d43eef71c96f0bb804f9e30211000000175eb576c5000000000000000000

1 output(s) for total of 18.999391141000 dcy

stealth address amount amount idx
00: 232ab26b4244e91f3213f1634ca1fa35d950cd7eb7d280a72827273d4384dd0d 18.999391141000 871361 of 0

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": 455510, "vin": [ { "gen": { "height": 455500 } } ], "vout": [ { "amount": 18999391141, "target": { "key": "232ab26b4244e91f3213f1634ca1fa35d950cd7eb7d280a72827273d4384dd0d" } } ], "extra": [ 1, 142, 125, 218, 159, 9, 55, 216, 131, 14, 142, 183, 132, 18, 237, 104, 87, 200, 196, 71, 68, 19, 212, 62, 239, 113, 201, 111, 11, 184, 4, 249, 227, 2, 17, 0, 0, 0, 23, 94, 181, 118, 197, 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