Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2140faa28b572911b0ad087d7be9675c05601f7034f50f0ae9ccf112a79c207f

Tx prefix hash: 61c356b04adcddbd801b3e5f3a7b84840b25071e565a9a3ee3a23306799bbf58
Tx public key: 33cd6ca9e0525eb5e5d24d7ae8caa0572e5556ea14c86334cf7e00605b03911f
Timestamp: 1721212084 Timestamp [UCT]: 2024-07-17 10:28:04 Age [y:d:h:m:s]: 00:220:17:38:19
Block: 1067615 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 157632 RingCT/type: yes/0
Extra: 0133cd6ca9e0525eb5e5d24d7ae8caa0572e5556ea14c86334cf7e00605b03911f02110000000991e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8737965c4e65152313e58a410cbf9277cd67ca50920a2e037a3ad895f6e26f07 0.600000000000 1538472 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": 1067625, "vin": [ { "gen": { "height": 1067615 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8737965c4e65152313e58a410cbf9277cd67ca50920a2e037a3ad895f6e26f07" } } ], "extra": [ 1, 51, 205, 108, 169, 224, 82, 94, 181, 229, 210, 77, 122, 232, 202, 160, 87, 46, 85, 86, 234, 20, 200, 99, 52, 207, 126, 0, 96, 91, 3, 145, 31, 2, 17, 0, 0, 0, 9, 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