Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 709b468f74274aad6de5a8592394681f11c06ec68fd22c5aa2ff0f239d60c086

Tx prefix hash: 84ed97021487c4e2ae847ee1f6f9b8a98a7ccc9358a6d08458198a006f0a3625
Tx public key: 2e28eccbb3e147e276cc738864080424f2f387703d0980d44c896428a455f022
Timestamp: 1721747452 Timestamp [UCT]: 2024-07-23 15:10:52 Age [y:d:h:m:s]: 00:171:14:55:46
Block: 1072034 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 122806 RingCT/type: yes/0
Extra: 012e28eccbb3e147e276cc738864080424f2f387703d0980d44c896428a455f0220211000000028f454fe7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bf727b75c357c0aad5656d826b1ab609f85e1bffa95f5e1cc7dd1b5aef7c9d76 0.600000000000 1544461 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": 1072044, "vin": [ { "gen": { "height": 1072034 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bf727b75c357c0aad5656d826b1ab609f85e1bffa95f5e1cc7dd1b5aef7c9d76" } } ], "extra": [ 1, 46, 40, 236, 203, 179, 225, 71, 226, 118, 204, 115, 136, 100, 8, 4, 36, 242, 243, 135, 112, 61, 9, 128, 212, 76, 137, 100, 40, 164, 85, 240, 34, 2, 17, 0, 0, 0, 2, 143, 69, 79, 231, 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