Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b948af9289236f47515f5867199725708766b9d3c1f0e08b7183279e5dccb55c

Tx prefix hash: b5afd65f7cc6e6966697a3f5c3c794f232be58afedf270a83f3dd2d5ef3aa4e5
Tx public key: 791997cda0bdca8f4439053eb6b73ddff9062b40951ef793e77040405d86e08e
Timestamp: 1759432419 Timestamp [UCT]: 2025-10-02 19:13:39 Age [y:d:h:m:s]: 00:005:12:38:08
Block: 1381346 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 3960 RingCT/type: yes/0
Extra: 01791997cda0bdca8f4439053eb6b73ddff9062b40951ef793e77040405d86e08e021100000003a5dccd79000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7d2f6a55d2feda7973062466a1676f818ae8ea6f8fa11d0c6655f94cfb72f3b4 0.600000000000 1869465 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": 1381356, "vin": [ { "gen": { "height": 1381346 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7d2f6a55d2feda7973062466a1676f818ae8ea6f8fa11d0c6655f94cfb72f3b4" } } ], "extra": [ 1, 121, 25, 151, 205, 160, 189, 202, 143, 68, 57, 5, 62, 182, 183, 61, 223, 249, 6, 43, 64, 149, 30, 247, 147, 231, 112, 64, 64, 93, 134, 224, 142, 2, 17, 0, 0, 0, 3, 165, 220, 205, 121, 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