Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b6352778f3faea31ccc2b44e56caace66e41e5c7504ad755e4ba9c99fef57897

Tx prefix hash: 1af7c6dcd7903cd921136b77d27fda2568ecf2d984c7e8fcfaed4d53e4be3de6
Tx public key: df626524fa12d96f5549a1a8ff3f2f399397b26e6097745e5a513c3cbf6fa385
Timestamp: 1762099694 Timestamp [UCT]: 2025-11-02 16:08:14 Age [y:d:h:m:s]: 00:013:16:25:32
Block: 1403456 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 9802 RingCT/type: yes/0
Extra: 01df626524fa12d96f5549a1a8ff3f2f399397b26e6097745e5a513c3cbf6fa385021100000003df5a247a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bb3228e13c21e61ad273e97000dd8759f44bfffeb16c46a5c67f48d740ed6821 0.600000000000 1891801 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": 1403466, "vin": [ { "gen": { "height": 1403456 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bb3228e13c21e61ad273e97000dd8759f44bfffeb16c46a5c67f48d740ed6821" } } ], "extra": [ 1, 223, 98, 101, 36, 250, 18, 217, 111, 85, 73, 161, 168, 255, 63, 47, 57, 147, 151, 178, 110, 96, 151, 116, 94, 90, 81, 60, 60, 191, 111, 163, 133, 2, 17, 0, 0, 0, 3, 223, 90, 36, 122, 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