Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 01fbf5753811f52801dfb10b1caa7bb52d70822727d16909217e4ecd3a553f90

Tx prefix hash: 3110eea9fff4a02361677895f0fd0694e92ca22258dcc1f13d85a08c3a3e7431
Tx public key: e10d1f87a383c5dd73894e2b84638384cf696111e54b1724ac19799dcb8d74e6
Timestamp: 1721562953 Timestamp [UCT]: 2024-07-21 11:55:53 Age [y:d:h:m:s]: 00:170:08:49:11
Block: 1070505 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 121905 RingCT/type: yes/0
Extra: 01e10d1f87a383c5dd73894e2b84638384cf696111e54b1724ac19799dcb8d74e6021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7d4d23a73012b1b1dc1f8f9c4d0dcd2203d29ee021c2b71b0e13828fa4b20304 0.600000000000 1542366 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": 1070515, "vin": [ { "gen": { "height": 1070505 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7d4d23a73012b1b1dc1f8f9c4d0dcd2203d29ee021c2b71b0e13828fa4b20304" } } ], "extra": [ 1, 225, 13, 31, 135, 163, 131, 197, 221, 115, 137, 78, 43, 132, 99, 131, 132, 207, 105, 97, 17, 229, 75, 23, 36, 172, 25, 121, 157, 203, 141, 116, 230, 2, 17, 0, 0, 0, 1, 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