Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 24e6498d4bb994220e8263a86572cd2b81a5458827d350300910752a4b04b8b4

Tx prefix hash: a5e98fa46b4ce4745e96e405ccff8c2748292c7c7b330ffdf2f8ad80dab0320c
Tx public key: 866097e31e2954b1ddde82c9fc0896dd364f87ed65f7dc8e0eb35a1b57d6f554
Timestamp: 1736813545 Timestamp [UCT]: 2025-01-14 00:12:25 Age [y:d:h:m:s]: 00:155:12:17:34
Block: 1196805 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 110852 RingCT/type: yes/0
Extra: 01866097e31e2954b1ddde82c9fc0896dd364f87ed65f7dc8e0eb35a1b57d6f554021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5f038197e7eae7f868c0b3370580a2105777e6102f6bf12ed143909b2871e715 0.600000000000 1683408 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": 1196815, "vin": [ { "gen": { "height": 1196805 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5f038197e7eae7f868c0b3370580a2105777e6102f6bf12ed143909b2871e715" } } ], "extra": [ 1, 134, 96, 151, 227, 30, 41, 84, 177, 221, 222, 130, 201, 252, 8, 150, 221, 54, 79, 135, 237, 101, 247, 220, 142, 14, 179, 90, 27, 87, 214, 245, 84, 2, 17, 0, 0, 0, 5, 0, 127, 151, 138, 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