Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6b698f6cafb7a30cfa8fd6393d9cd1046444d4173b388844f6577c6c761b7fe1

Tx prefix hash: 82629afcd30ff05f82112d93bec46b8fb4b632392ef190454633e9c3dd30f62d
Tx public key: 6087f13870303352b796e513a4e1e8971ed70e73d3de1d7c178fa3de0f7b67d8
Timestamp: 1750465046 Timestamp [UCT]: 2025-06-21 00:17:26 Age [y:d:h:m:s]: 00:148:04:09:30
Block: 1309394 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 103745 RingCT/type: yes/0
Extra: 016087f13870303352b796e513a4e1e8971ed70e73d3de1d7c178fa3de0f7b67d8021100000001d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a75b06e8f10e00bbd64369b7af808ca120ab42b6bf27a72a67a362b670b4d674 0.600000000000 1797009 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": 1309404, "vin": [ { "gen": { "height": 1309394 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a75b06e8f10e00bbd64369b7af808ca120ab42b6bf27a72a67a362b670b4d674" } } ], "extra": [ 1, 96, 135, 241, 56, 112, 48, 51, 82, 183, 150, 229, 19, 164, 225, 232, 151, 30, 215, 14, 115, 211, 222, 29, 124, 23, 143, 163, 222, 15, 123, 103, 216, 2, 17, 0, 0, 0, 1, 216, 231, 210, 65, 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