Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 928414c7668ab1193d81ec92c9b2ca4107fb98b95e1b35121e517b25d84902ee

Tx prefix hash: f5b1da22c4ecd0766a094ea083ab805eabc9567e6f3cd9e3b84d8779a00772b6
Tx public key: 8c3b6bab936dce81ada0d6d7aa47ede37eb2d1ae13ff40a1818dfb3658371c0a
Timestamp: 1764155724 Timestamp [UCT]: 2025-11-26 11:15:24 Age [y:d:h:m:s]: 00:000:02:06:26
Block: 1420500 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 60 RingCT/type: yes/0
Extra: 018c3b6bab936dce81ada0d6d7aa47ede37eb2d1ae13ff40a1818dfb3658371c0a0211000000024e7bfc09000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 06c3d48e5b1871cbfdde334225418df89a248fabd2a54fe5acef0f331fe7aaa3 0.600000000000 1909043 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": 1420510, "vin": [ { "gen": { "height": 1420500 } } ], "vout": [ { "amount": 600000000, "target": { "key": "06c3d48e5b1871cbfdde334225418df89a248fabd2a54fe5acef0f331fe7aaa3" } } ], "extra": [ 1, 140, 59, 107, 171, 147, 109, 206, 129, 173, 160, 214, 215, 170, 71, 237, 227, 126, 178, 209, 174, 19, 255, 64, 161, 129, 141, 251, 54, 88, 55, 28, 10, 2, 17, 0, 0, 0, 2, 78, 123, 252, 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