Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 006844a163b4bc39e6ac2d72e32ef45da5bfbb40574e7ade11f5b71d76d1d67f

Tx prefix hash: 7ea249aa723606418e27ce0fb9976fa67feae05dbc76382dae60663bb556c0c1
Tx public key: dae249da62bca1cf29b5e86f0e9aff691e77fd95874c4135a1263c15c11c17c5
Timestamp: 1708852113 Timestamp [UCT]: 2024-02-25 09:08:33 Age [y:d:h:m:s]: 01:049:04:12:28
Block: 965139 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 296167 RingCT/type: yes/0
Extra: 01dae249da62bca1cf29b5e86f0e9aff691e77fd95874c4135a1263c15c11c17c50211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ea723e2f93e4ab151b1f38826ead54c5557be4dd625031e565c43e0eb2127ca7 0.600000000000 1424888 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": 965149, "vin": [ { "gen": { "height": 965139 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ea723e2f93e4ab151b1f38826ead54c5557be4dd625031e565c43e0eb2127ca7" } } ], "extra": [ 1, 218, 226, 73, 218, 98, 188, 161, 207, 41, 181, 232, 111, 14, 154, 255, 105, 30, 119, 253, 149, 135, 76, 65, 53, 161, 38, 60, 21, 193, 28, 23, 197, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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