Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 641e7dcbae6f6b290017ff6ef2a88abdfbc4a18d5d79124a0eb17f13bd464b00

Tx prefix hash: 43ebd4abdecfe64e9a4f92d3e0227799e04d89f2017187ab19c880ad2493e6eb
Tx public key: 090f94c9c9682f604febbe2f28b942cc0a1e3609a0035b6cbe2cf7332a000c07
Timestamp: 1635626972 Timestamp [UCT]: 2021-10-30 20:49:32 Age [y:d:h:m:s]: 03:032:05:45:17
Block: 363859 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 801547 RingCT/type: yes/0
Extra: 01090f94c9c9682f604febbe2f28b942cc0a1e3609a0035b6cbe2cf7332a000c07021100000013328bb496000000000000000000

1 output(s) for total of 38.228916491000 dcy

stealth address amount amount idx
00: b59022b8c8c8de297a2fa250a31ed9cd5f06bc82429f9866bc76a1572b9f8f6c 38.228916491000 739385 of 0

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": 363869, "vin": [ { "gen": { "height": 363859 } } ], "vout": [ { "amount": 38228916491, "target": { "key": "b59022b8c8c8de297a2fa250a31ed9cd5f06bc82429f9866bc76a1572b9f8f6c" } } ], "extra": [ 1, 9, 15, 148, 201, 201, 104, 47, 96, 79, 235, 190, 47, 40, 185, 66, 204, 10, 30, 54, 9, 160, 3, 91, 108, 190, 44, 247, 51, 42, 0, 12, 7, 2, 17, 0, 0, 0, 19, 50, 139, 180, 150, 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