Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4c6fb9a4d17852ba61ec1a6efedd6ce8680b3f273fb6a228eccdbfc8ca45f022

Tx prefix hash: d0634a899546ce2c8129b6ae772fdf9c0aeaf30803552792565e8b9b8b83b26c
Tx public key: d4a45482b9a809860c48a6edfe510a7b228b14a1558e857e4047dff962323461
Timestamp: 1758331730 Timestamp [UCT]: 2025-09-20 01:28:50 Age [y:d:h:m:s]: 00:098:11:04:16
Block: 1372229 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 70500 RingCT/type: yes/0
Extra: 01d4a45482b9a809860c48a6edfe510a7b228b14a1558e857e4047dff962323461021100000003b2f784c4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: eb456e8eceb520b4790c3900c7a8f55765a55643bcbda0899112d1228bc3f066 0.600000000000 1860314 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": 1372239, "vin": [ { "gen": { "height": 1372229 } } ], "vout": [ { "amount": 600000000, "target": { "key": "eb456e8eceb520b4790c3900c7a8f55765a55643bcbda0899112d1228bc3f066" } } ], "extra": [ 1, 212, 164, 84, 130, 185, 168, 9, 134, 12, 72, 166, 237, 254, 81, 10, 123, 34, 139, 20, 161, 85, 142, 133, 126, 64, 71, 223, 249, 98, 50, 52, 97, 2, 17, 0, 0, 0, 3, 178, 247, 132, 196, 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