Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 51253c2798be2b3afde6de049be1444cad7a1193a24cd1a8eda7e6885652152d

Tx prefix hash: b605d6acbb42b2d9b7e85721ac1e2d06c398c2bf17f5b77192fadb4a9fbf6b23
Tx public key: f05501a0e9d8d824edfc8221c1b7b8aa6df734667beaa9f7635e96c3a8d47051
Timestamp: 1763250892 Timestamp [UCT]: 2025-11-15 23:54:52 Age [y:d:h:m:s]: 00:077:10:53:17
Block: 1413006 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 55268 RingCT/type: yes/0
Extra: 01f05501a0e9d8d824edfc8221c1b7b8aa6df734667beaa9f7635e96c3a8d47051021100000001da554848000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dbbfefb4ef1255f56a8d93027b6df5a2abc938c9a0dd6a4d9c1abca2dc72b358 0.600000000000 1901483 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": 1413016, "vin": [ { "gen": { "height": 1413006 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dbbfefb4ef1255f56a8d93027b6df5a2abc938c9a0dd6a4d9c1abca2dc72b358" } } ], "extra": [ 1, 240, 85, 1, 160, 233, 216, 216, 36, 237, 252, 130, 33, 193, 183, 184, 170, 109, 247, 52, 102, 123, 234, 169, 247, 99, 94, 150, 195, 168, 212, 112, 81, 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