Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 89a3fec24273754aa22046ee0a0d93964df6d9565dc55a8896eac45cf452d64c

Tx prefix hash: 7f7f9df92712efd9b3df60657b0765edf767a4818bc6a0a02b5c472a289958e6
Tx public key: 45ed1c4acc79797bf1f9e5e28eae030572d8a2969666c40375cdac3db98d5ab0
Timestamp: 1755865408 Timestamp [UCT]: 2025-08-22 12:23:28 Age [y:d:h:m:s]: 00:043:06:53:35
Block: 1351973 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 30809 RingCT/type: yes/0
Extra: 0145ed1c4acc79797bf1f9e5e28eae030572d8a2969666c40375cdac3db98d5ab00211000000072609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 01310f92cb56ac7eefad6ecceab02f2b78ad16eabc2133014cb0b2a6bf44395a 0.600000000000 1839934 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": 1351983, "vin": [ { "gen": { "height": 1351973 } } ], "vout": [ { "amount": 600000000, "target": { "key": "01310f92cb56ac7eefad6ecceab02f2b78ad16eabc2133014cb0b2a6bf44395a" } } ], "extra": [ 1, 69, 237, 28, 74, 204, 121, 121, 123, 241, 249, 229, 226, 142, 174, 3, 5, 114, 216, 162, 150, 150, 102, 196, 3, 117, 205, 172, 61, 185, 141, 90, 176, 2, 17, 0, 0, 0, 7, 38, 9, 179, 160, 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