Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8e30637e150dc6c94961101f37f3175aac69302fd49cee05b5fb80eff0025e7a

Tx prefix hash: a2ff09160e9bfb60b774277f16e49165433d4b90b05cfbe779ec355a43a154a6
Tx public key: d6cda4e3d01796bc49169dda948959fce3e20164d60495dcb336c9b686b9ba2f
Timestamp: 1714176795 Timestamp [UCT]: 2024-04-27 00:13:15 Age [y:d:h:m:s]: 00:344:23:30:29
Block: 1009268 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 246607 RingCT/type: yes/0
Extra: 01d6cda4e3d01796bc49169dda948959fce3e20164d60495dcb336c9b686b9ba2f02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 17ca785b2c0f4437536bdb0ae4d6cf0e303c8c7b53af4af4d3eab139c04125d6 0.600000000000 1470892 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": 1009278, "vin": [ { "gen": { "height": 1009268 } } ], "vout": [ { "amount": 600000000, "target": { "key": "17ca785b2c0f4437536bdb0ae4d6cf0e303c8c7b53af4af4d3eab139c04125d6" } } ], "extra": [ 1, 214, 205, 164, 227, 208, 23, 150, 188, 73, 22, 157, 218, 148, 137, 89, 252, 227, 226, 1, 100, 214, 4, 149, 220, 179, 54, 201, 182, 134, 185, 186, 47, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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