Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 11b768be3e041b0d11b70c15f05949d67c0f312846fb67fd01d83e74a3cd6aff

Tx prefix hash: 521c680f73232d71b33c1c0f377aad0629de6208ecd8721012ae047d01a1ee0a
Tx public key: 82c543eea07f1a9daea4773ab0736d9f08aa8292f64499d1ec91022d6c6556a7
Timestamp: 1760911312 Timestamp [UCT]: 2025-10-19 22:01:52 Age [y:d:h:m:s]: 00:104:13:54:05
Block: 1393629 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 74678 RingCT/type: yes/0
Extra: 0182c543eea07f1a9daea4773ab0736d9f08aa8292f64499d1ec91022d6c6556a702110000001325a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 64759cc3541bb75f0cc8fdcd449469b25d65edd67372e2bf1d68a86e4d2a9e05 0.600000000000 1881894 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": 1393639, "vin": [ { "gen": { "height": 1393629 } } ], "vout": [ { "amount": 600000000, "target": { "key": "64759cc3541bb75f0cc8fdcd449469b25d65edd67372e2bf1d68a86e4d2a9e05" } } ], "extra": [ 1, 130, 197, 67, 238, 160, 127, 26, 157, 174, 164, 119, 58, 176, 115, 109, 159, 8, 170, 130, 146, 246, 68, 153, 209, 236, 145, 2, 45, 108, 101, 86, 167, 2, 17, 0, 0, 0, 19, 37, 163, 90, 15, 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