Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ed10085970efdc08228c4553f11cbe9816c3325d954a4a0997b7211932be179f

Tx prefix hash: 61bc8be47d6b6b22116a2f84fb7c188018562578ddedc3bcd0e8ee36de8c1927
Tx public key: 8241d45487f459a8c280cb6cf3e2dae2dbb4740eb9f68f7fca4da40120d4e8a4
Timestamp: 1730508667 Timestamp [UCT]: 2024-11-02 00:51:07 Age [y:d:h:m:s]: 00:006:00:09:06
Block: 1144588 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 4308 RingCT/type: yes/0
Extra: 018241d45487f459a8c280cb6cf3e2dae2dbb4740eb9f68f7fca4da40120d4e8a40211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1751ea557c36bd1a1fa6742974b86fb4ec5d82d9cc1f1a7ae046a8216ccaa852 0.600000000000 1628847 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": 1144598, "vin": [ { "gen": { "height": 1144588 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1751ea557c36bd1a1fa6742974b86fb4ec5d82d9cc1f1a7ae046a8216ccaa852" } } ], "extra": [ 1, 130, 65, 212, 84, 135, 244, 89, 168, 194, 128, 203, 108, 243, 226, 218, 226, 219, 180, 116, 14, 185, 246, 143, 127, 202, 77, 164, 1, 32, 212, 232, 164, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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