Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4a9f0fbefb29d157ddfd6af239775d5a9728a03ca2d32f4781f6d811c7e02545

Tx prefix hash: 60def57c5939082c809aa995ce577745bfcde9f4319e589f8f862b4082803f49
Tx public key: e75c69366009aa4837fdf2d0007f080ebf4ebace8c03873b82932219e2322284
Timestamp: 1726278595 Timestamp [UCT]: 2024-09-14 01:49:55 Age [y:d:h:m:s]: 00:162:08:53:27
Block: 1109611 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 115835 RingCT/type: yes/0
Extra: 01e75c69366009aa4837fdf2d0007f080ebf4ebace8c03873b82932219e2322284021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6fd1b8c824e68a7990efe1b94325297588c2c0118b4031b1b2faf4be38df0ba6 0.600000000000 1587922 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": 1109621, "vin": [ { "gen": { "height": 1109611 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6fd1b8c824e68a7990efe1b94325297588c2c0118b4031b1b2faf4be38df0ba6" } } ], "extra": [ 1, 231, 92, 105, 54, 96, 9, 170, 72, 55, 253, 242, 208, 0, 127, 8, 14, 191, 78, 186, 206, 140, 3, 135, 59, 130, 147, 34, 25, 226, 50, 34, 132, 2, 17, 0, 0, 0, 5, 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