Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b35394ad25dc43b8f3ab6b725113a76a06df7b44cf29672ba4b7620c73f4a4a5

Tx prefix hash: 20e6703c7b37390dfa5be074d76eac018b34f1c8e408c558143b76c03d7a2699
Tx public key: 2661ab46f6cd86cfc906cbe1c6abe2999c9ab78efc1274f92c7b3c8cf34c0a84
Timestamp: 1750456795 Timestamp [UCT]: 2025-06-20 21:59:55 Age [y:d:h:m:s]: 00:149:16:44:43
Block: 1309321 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 104837 RingCT/type: yes/0
Extra: 012661ab46f6cd86cfc906cbe1c6abe2999c9ab78efc1274f92c7b3c8cf34c0a84021100000002d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cc3b63098eeee5fe1fafba140c2b8cf32cb98a3ed48380911ecc587be731e460 0.600000000000 1796936 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": 1309331, "vin": [ { "gen": { "height": 1309321 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cc3b63098eeee5fe1fafba140c2b8cf32cb98a3ed48380911ecc587be731e460" } } ], "extra": [ 1, 38, 97, 171, 70, 246, 205, 134, 207, 201, 6, 203, 225, 198, 171, 226, 153, 156, 154, 183, 142, 252, 18, 116, 249, 44, 123, 60, 140, 243, 76, 10, 132, 2, 17, 0, 0, 0, 2, 216, 231, 210, 65, 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