Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4af08454b66e8562e6dfb7a459b83ffb128dab918827b6bcb04d3c324007bc9d

Tx prefix hash: d5a81685f8e002d65b57d94cde75d77e245926a084c9bc4e98ff4afc63467ad0
Tx public key: d5904c4f3cb2cc36132bfa77427b6994d62e3e27f9cb0d64552da836ea08dc93
Timestamp: 1764253824 Timestamp [UCT]: 2025-11-27 14:30:24 Age [y:d:h:m:s]: 00:024:04:38:01
Block: 1421316 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 17312 RingCT/type: yes/0
Extra: 01d5904c4f3cb2cc36132bfa77427b6994d62e3e27f9cb0d64552da836ea08dc930211000000e8d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c2baed25901e97ee1ab8a299a82f1511ce9871b77a6ee3482fffe35280b8460f 0.600000000000 1909873 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": 1421326, "vin": [ { "gen": { "height": 1421316 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c2baed25901e97ee1ab8a299a82f1511ce9871b77a6ee3482fffe35280b8460f" } } ], "extra": [ 1, 213, 144, 76, 79, 60, 178, 204, 54, 19, 43, 250, 119, 66, 123, 105, 148, 214, 46, 62, 39, 249, 203, 13, 100, 85, 45, 168, 54, 234, 8, 220, 147, 2, 17, 0, 0, 0, 232, 214, 225, 157, 124, 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