Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ada296bfbc0e0ab57e8ecdc5eaa64f60a76cb87092ce26e548a4c88cb674fcee

Tx prefix hash: ba3bac170a4ee23a7f41b6d55fff7d777dc9fc56b5d4a34be50f549e0335923b
Tx public key: 525ef5b1649827b525ba8dad4229c9651573e58a66fb1071e6b1b65252718a0c
Timestamp: 1763300601 Timestamp [UCT]: 2025-11-16 13:43:21 Age [y:d:h:m:s]: 00:037:07:01:51
Block: 1413403 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 26705 RingCT/type: yes/0
Extra: 01525ef5b1649827b525ba8dad4229c9651573e58a66fb1071e6b1b65252718a0c02110000000243b50471000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e5f8a287e10595908d712f753403dbdfdb840cde5bfe0e532721e114f6d698f4 0.600000000000 1901882 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": 1413413, "vin": [ { "gen": { "height": 1413403 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e5f8a287e10595908d712f753403dbdfdb840cde5bfe0e532721e114f6d698f4" } } ], "extra": [ 1, 82, 94, 245, 177, 100, 152, 39, 181, 37, 186, 141, 173, 66, 41, 201, 101, 21, 115, 229, 138, 102, 251, 16, 113, 230, 177, 182, 82, 82, 113, 138, 12, 2, 17, 0, 0, 0, 2, 67, 181, 4, 113, 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