Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4805eff3d00ef91cf56669971995c69907c7e343aa97f2e3dcfa1133657866d1

Tx prefix hash: 4093aa570914ea471884a530ab923f9a5db45e0d7c0ee070089326f1c0aa3c96
Tx public key: 709507ad458b317d3cb82294e2a45442d1eab79b07f6cb490822e0777bd2f657
Timestamp: 1745818160 Timestamp [UCT]: 2025-04-28 05:29:20 Age [y:d:h:m:s]: 00:200:12:45:10
Block: 1271092 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 141023 RingCT/type: yes/0
Extra: 01709507ad458b317d3cb82294e2a45442d1eab79b07f6cb490822e0777bd2f65702110000000225a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 348f5bc60bf06c4e28ec36a79a5f74312ed768ec1be2bcb39fe0fcc574dc4716 0.600000000000 1758339 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": 1271102, "vin": [ { "gen": { "height": 1271092 } } ], "vout": [ { "amount": 600000000, "target": { "key": "348f5bc60bf06c4e28ec36a79a5f74312ed768ec1be2bcb39fe0fcc574dc4716" } } ], "extra": [ 1, 112, 149, 7, 173, 69, 139, 49, 125, 60, 184, 34, 148, 226, 164, 84, 66, 209, 234, 183, 155, 7, 246, 203, 73, 8, 34, 224, 119, 123, 210, 246, 87, 2, 17, 0, 0, 0, 2, 37, 163, 90, 15, 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