Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0217a7423d2772b314737a248c31e1516c1359665ea3669db41a6f66cdc0cbcb

Tx prefix hash: bc23ceb8dc844e45be84af3ad10a610eab267f679431f9ac41ec5b5f83ea101d
Tx public key: 2308cbed0d1be5a5d5bbe715bceefd68acf8bdd377ce3115066cca73e800d5fd
Timestamp: 1697320865 Timestamp [UCT]: 2023-10-14 22:01:05 Age [y:d:h:m:s]: 02:022:20:17:39
Block: 869741 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 535926 RingCT/type: yes/0
Extra: 012308cbed0d1be5a5d5bbe715bceefd68acf8bdd377ce3115066cca73e800d5fd0211000000014b8f5122000000000000000000

1 output(s) for total of 0.805725388000 dcy

stealth address amount amount idx
00: 8d10f96b50e703b716ccb87252701b11e0cd5e66d14c0d7328a7f7289a105288 0.805725388000 1324596 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": 869751, "vin": [ { "gen": { "height": 869741 } } ], "vout": [ { "amount": 805725388, "target": { "key": "8d10f96b50e703b716ccb87252701b11e0cd5e66d14c0d7328a7f7289a105288" } } ], "extra": [ 1, 35, 8, 203, 237, 13, 27, 229, 165, 213, 187, 231, 21, 188, 238, 253, 104, 172, 248, 189, 211, 119, 206, 49, 21, 6, 108, 202, 115, 232, 0, 213, 253, 2, 17, 0, 0, 0, 1, 75, 143, 81, 34, 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