Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 57e39b1a5a7674eaf6c2c11b5be7cafad5d05cec5748b054fd9ce1ab99e09536

Tx prefix hash: b8ab24b0cc37a59471e9e08aeb0820b94dac5dfc763b2ff6591209108cc9ce7b
Tx public key: f8015cd4a1f1ccc633ea3b86fbfeb002a2861867c9fe5013c4d735a62e3196a1
Timestamp: 1762031283 Timestamp [UCT]: 2025-11-01 21:08:03 Age [y:d:h:m:s]: 00:007:03:48:53
Block: 1402898 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 5117 RingCT/type: yes/0
Extra: 01f8015cd4a1f1ccc633ea3b86fbfeb002a2861867c9fe5013c4d735a62e3196a1021100000001e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f752b318b708912bc3246df7eac3d964100ffddee44bd39d06e21aa74fc8ceba 0.600000000000 1891223 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": 1402908, "vin": [ { "gen": { "height": 1402898 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f752b318b708912bc3246df7eac3d964100ffddee44bd39d06e21aa74fc8ceba" } } ], "extra": [ 1, 248, 1, 92, 212, 161, 241, 204, 198, 51, 234, 59, 134, 251, 254, 176, 2, 162, 134, 24, 103, 201, 254, 80, 19, 196, 215, 53, 166, 46, 49, 150, 161, 2, 17, 0, 0, 0, 1, 228, 220, 144, 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