Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c16cbdf6bf9ca77d64d89b2436224691d869446758982f7b44226a65b36dd38d

Tx prefix hash: 8fbbefe620149cd6301a60b8d8a2ba3fa8590c7cab61c99fac0c66feaaad1854
Tx public key: a193eeb5495d5f27aa5c792ddba6e9c0f509123d28cbf95e27668a712e9909b6
Timestamp: 1763579108 Timestamp [UCT]: 2025-11-19 19:05:08 Age [y:d:h:m:s]: 00:048:02:40:48
Block: 1415716 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 34455 RingCT/type: yes/0
Extra: 01a193eeb5495d5f27aa5c792ddba6e9c0f509123d28cbf95e27668a712e9909b602110000000170609d03000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 00d37c56e0aa1e4898b8e53c4dae0bd029c5caaedc322449f8a9858eeb78bcaf 0.600000000000 1904221 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": 1415726, "vin": [ { "gen": { "height": 1415716 } } ], "vout": [ { "amount": 600000000, "target": { "key": "00d37c56e0aa1e4898b8e53c4dae0bd029c5caaedc322449f8a9858eeb78bcaf" } } ], "extra": [ 1, 161, 147, 238, 181, 73, 93, 95, 39, 170, 92, 121, 45, 219, 166, 233, 192, 245, 9, 18, 61, 40, 203, 249, 94, 39, 102, 138, 113, 46, 153, 9, 182, 2, 17, 0, 0, 0, 1, 112, 96, 157, 3, 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