Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e2851320d7b261109adf65e6c10d7f1357b16e5660d74bca4678434367b7ec0c

Tx prefix hash: 6ec2df8bfc27741d70fa4821b1f8f4401ea7b3315c499f8c3373084fe3f929fa
Tx public key: 5a9273b3b9ae1872fc1f4d4157da22f5380f0c6f81c3b104326202f9dca6761d
Timestamp: 1713690016 Timestamp [UCT]: 2024-04-21 09:00:16 Age [y:d:h:m:s]: 00:350:07:39:58
Block: 1005238 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 250433 RingCT/type: yes/0
Extra: 015a9273b3b9ae1872fc1f4d4157da22f5380f0c6f81c3b104326202f9dca6761d0211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ed8a56476dd0324cb56c6efa4a2e37b2ae0a5ff16c5e1c25fc8fc75a95b6e7f0 0.600000000000 1465822 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": 1005248, "vin": [ { "gen": { "height": 1005238 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ed8a56476dd0324cb56c6efa4a2e37b2ae0a5ff16c5e1c25fc8fc75a95b6e7f0" } } ], "extra": [ 1, 90, 146, 115, 179, 185, 174, 24, 114, 252, 31, 77, 65, 87, 218, 34, 245, 56, 15, 12, 111, 129, 195, 177, 4, 50, 98, 2, 249, 220, 166, 118, 29, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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