Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4cdd6acc0f717c29a285b214bd984755a399b425b70524e21ad4a1e26da3df5b

Tx prefix hash: 14bd1a9367376c525c95e4a0552ef4cbd42c0a0ba2259f926302ab2011286342
Tx public key: a2e51a95bc4a52c54e9f9c76cc813d2452c40f541bd778d8b564cd9e477f91e2
Timestamp: 1761934529 Timestamp [UCT]: 2025-10-31 18:15:29 Age [y:d:h:m:s]: 00:008:05:14:38
Block: 1402101 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 5871 RingCT/type: yes/0
Extra: 01a2e51a95bc4a52c54e9f9c76cc813d2452c40f541bd778d8b564cd9e477f91e20211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dd8104b14bc9b1ad744b9f23133f7d15ee9356f25e92bcec41914e0fa4fb65d7 0.600000000000 1890420 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": 1402111, "vin": [ { "gen": { "height": 1402101 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dd8104b14bc9b1ad744b9f23133f7d15ee9356f25e92bcec41914e0fa4fb65d7" } } ], "extra": [ 1, 162, 229, 26, 149, 188, 74, 82, 197, 78, 159, 156, 118, 204, 129, 61, 36, 82, 196, 15, 84, 27, 215, 120, 216, 181, 100, 205, 158, 71, 127, 145, 226, 2, 17, 0, 0, 0, 1, 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