Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9da9e894b885a2590aa5faa8ee74468bbcc7cd576fa9fbef66b76c8174741ae4

Tx prefix hash: de473de72719ac5d7ded23d41f0a6943b593ef3ee7674fb85cc9b71a7b8c3968
Tx public key: e8ee55ec2545ec07b95df219b4fa12a3babe62d31ef9dae82426b8fb5d86afef
Timestamp: 1734645437 Timestamp [UCT]: 2024-12-19 21:57:17 Age [y:d:h:m:s]: 00:102:11:24:22
Block: 1178884 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 72993 RingCT/type: yes/0
Extra: 01e8ee55ec2545ec07b95df219b4fa12a3babe62d31ef9dae82426b8fb5d86afef0211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9a8a884da00a5eaba53a7f2ddc88439732d7d48ffaad350f693d0eb1ceab01d6 0.600000000000 1665273 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": 1178894, "vin": [ { "gen": { "height": 1178884 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9a8a884da00a5eaba53a7f2ddc88439732d7d48ffaad350f693d0eb1ceab01d6" } } ], "extra": [ 1, 232, 238, 85, 236, 37, 69, 236, 7, 185, 93, 242, 25, 180, 250, 18, 163, 186, 190, 98, 211, 30, 249, 218, 232, 36, 38, 184, 251, 93, 134, 175, 239, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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