Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 08f4a9054f32de3a3d5168ae2719a5bed59e8c505ecc7a0100255db5200ffa43

Tx prefix hash: 0126c4f80a3e394c8e5762f428f9701872ee7cdf0a89997129631dc55ab52c83
Tx public key: 7690b69ef87b9644adcef6f69e70a732561f63f3af5a14adf944abd18d8aa6f2
Timestamp: 1749795504 Timestamp [UCT]: 2025-06-13 06:18:24 Age [y:d:h:m:s]: 00:161:17:43:28
Block: 1303964 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 113330 RingCT/type: yes/0
Extra: 017690b69ef87b9644adcef6f69e70a732561f63f3af5a14adf944abd18d8aa6f2021100000002e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3e2b66b45276908e529a345f791764943192e8476ae09ff33e8c7708f5a6a9c0 0.600000000000 1791549 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": 1303974, "vin": [ { "gen": { "height": 1303964 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3e2b66b45276908e529a345f791764943192e8476ae09ff33e8c7708f5a6a9c0" } } ], "extra": [ 1, 118, 144, 182, 158, 248, 123, 150, 68, 173, 206, 246, 246, 158, 112, 167, 50, 86, 31, 99, 243, 175, 90, 20, 173, 249, 68, 171, 209, 141, 138, 166, 242, 2, 17, 0, 0, 0, 2, 228, 220, 144, 9, 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