Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3ae8f91a568e9e342aea0c70bf0ca9b8bc409b9e29715224d3b04315e8e104b3

Tx prefix hash: b4d2994645acf56627a3ed06a3afd75373cff19156d717730eb66f3fcf8515d9
Tx public key: 1bfff19bb4fabbfe92e92dc704cce6b63d36a03b905ff5aedfa54b381bd5757d
Timestamp: 1749665992 Timestamp [UCT]: 2025-06-11 18:19:52 Age [y:d:h:m:s]: 00:155:02:01:43
Block: 1302929 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 108533 RingCT/type: yes/0
Extra: 011bfff19bb4fabbfe92e92dc704cce6b63d36a03b905ff5aedfa54b381bd5757d021100000002e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c57c0d01ff8d6d4144fa5eff8479e2405c0056a71a8fae8261565cc5b9107e22 0.600000000000 1790504 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": 1302939, "vin": [ { "gen": { "height": 1302929 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c57c0d01ff8d6d4144fa5eff8479e2405c0056a71a8fae8261565cc5b9107e22" } } ], "extra": [ 1, 27, 255, 241, 155, 180, 250, 187, 254, 146, 233, 45, 199, 4, 204, 230, 182, 61, 54, 160, 59, 144, 95, 245, 174, 223, 165, 75, 56, 27, 213, 117, 125, 2, 17, 0, 0, 0, 2, 228, 220, 144, 9, 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