Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8d8a3ff15d6260616b62532a8831bf7f05db0fa7cb1f0f7c9c7480315c7d5a8b

Tx prefix hash: 05501cb277a7ad1365a18eae8d5996fb9f4b84cc6dc6f324982d95f024aecd4c
Tx public key: 7bd211924271e3e1a39ce3e28a0511ae89deeda054812739742c3220f9df6ccf
Timestamp: 1724502137 Timestamp [UCT]: 2024-08-24 12:22:17 Age [y:d:h:m:s]: 01:045:18:53:48
Block: 1094896 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 291106 RingCT/type: yes/0
Extra: 017bd211924271e3e1a39ce3e28a0511ae89deeda054812739742c3220f9df6ccf021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ed08986f81a0b0792547c55b966eaf261911ecd95fe1c2c0599f7c4bf6ff822e 0.600000000000 1570017 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": 1094906, "vin": [ { "gen": { "height": 1094896 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ed08986f81a0b0792547c55b966eaf261911ecd95fe1c2c0599f7c4bf6ff822e" } } ], "extra": [ 1, 123, 210, 17, 146, 66, 113, 227, 225, 163, 156, 227, 226, 138, 5, 17, 174, 137, 222, 237, 160, 84, 129, 39, 57, 116, 44, 50, 32, 249, 223, 108, 207, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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