Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 30ed6e3a2e7a45f3af268c4c5ecc9c11fd9bc311ac5c764261d1fb7c82e1de63

Tx prefix hash: 604f7918f92c55559613d28972ba7130954672b9b288759e497af8a58976fbf3
Tx public key: f0c656795f7a4e1a8d3b60b1fae695abdc11c46946b05f67c3c61ba5de4a4bf1
Timestamp: 1727163835 Timestamp [UCT]: 2024-09-24 07:43:55 Age [y:d:h:m:s]: 00:195:01:06:39
Block: 1116954 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 139198 RingCT/type: yes/0
Extra: 01f0c656795f7a4e1a8d3b60b1fae695abdc11c46946b05f67c3c61ba5de4a4bf102110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 523d6ef4ada75ae7784a80921f25c8f6b5ba233f35c133bb31c3dbf9d3ede012 0.600000000000 1597617 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": 1116964, "vin": [ { "gen": { "height": 1116954 } } ], "vout": [ { "amount": 600000000, "target": { "key": "523d6ef4ada75ae7784a80921f25c8f6b5ba233f35c133bb31c3dbf9d3ede012" } } ], "extra": [ 1, 240, 198, 86, 121, 95, 122, 78, 26, 141, 59, 96, 177, 250, 230, 149, 171, 220, 17, 196, 105, 70, 176, 95, 103, 195, 198, 27, 165, 222, 74, 75, 241, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 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