Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0069f7007303edef2d883a47c908a08ff6f55f52385123e443426972a19ae101

Tx prefix hash: bd2d97f6cb7fc28352f1811c225a1757cf6efdda0e899cac1f61546074ed8e6c
Tx public key: e15b997a95120c6424b4f8c440746168ffd94af05576b2e00f0ef82cbf4ab3a6
Timestamp: 1706762244 Timestamp [UCT]: 2024-02-01 04:37:24 Age [y:d:h:m:s]: 00:325:16:03:21
Block: 947787 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 233213 RingCT/type: yes/0
Extra: 01e15b997a95120c6424b4f8c440746168ffd94af05576b2e00f0ef82cbf4ab3a602110000000e0011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8bd85192d5a80a981c599b8dc044f2be1d4912a4c65382b801cbda5c5b3cd830 0.600000000000 1406145 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": 947797, "vin": [ { "gen": { "height": 947787 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8bd85192d5a80a981c599b8dc044f2be1d4912a4c65382b801cbda5c5b3cd830" } } ], "extra": [ 1, 225, 91, 153, 122, 149, 18, 12, 100, 36, 180, 248, 196, 64, 116, 97, 104, 255, 217, 74, 240, 85, 118, 178, 224, 15, 14, 248, 44, 191, 74, 179, 166, 2, 17, 0, 0, 0, 14, 0, 17, 5, 91, 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