Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a6caa84c9af4cea49f0e1e895c857cd7b1d4fe948029a539a137ae38ec5c51e0

Tx prefix hash: 25fc3361e279740c2ff523bdf3c6180fa99a72b3b77cf76c4e1a248096d40c75
Tx public key: 16dfd7f66f786707616d614a4a0e583c55e54cec1dfe8369837f181c76020c35
Timestamp: 1763422560 Timestamp [UCT]: 2025-11-17 23:36:00 Age [y:d:h:m:s]: 00:003:00:06:37
Block: 1414421 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 2145 RingCT/type: yes/0
Extra: 0116dfd7f66f786707616d614a4a0e583c55e54cec1dfe8369837f181c76020c35021100000001da554848000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b11db3f37ff92a383871754721e0b8e9ac3c0dcb043fcf9f8b7aed149231c9e9 0.600000000000 1902910 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": 1414431, "vin": [ { "gen": { "height": 1414421 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b11db3f37ff92a383871754721e0b8e9ac3c0dcb043fcf9f8b7aed149231c9e9" } } ], "extra": [ 1, 22, 223, 215, 246, 111, 120, 103, 7, 97, 109, 97, 74, 74, 14, 88, 60, 85, 229, 76, 236, 29, 254, 131, 105, 131, 127, 24, 28, 118, 2, 12, 53, 2, 17, 0, 0, 0, 1, 218, 85, 72, 72, 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