Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c4bb4e1b4bd0eec5240cb09beecc8e526e57e0b5cd8982d54a154101cd77cb2f

Tx prefix hash: 62d64253ce838d1ef18f00d10d119a170dda8ea4918cfc2621eaf57a22601d73
Tx public key: 332f9e035574ccd5efa5bf3d2ccf50128659a819fb7646d3d57179f5b80078c2
Timestamp: 1699667660 Timestamp [UCT]: 2023-11-11 01:54:20 Age [y:d:h:m:s]: 01:139:16:29:14
Block: 889000 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 361012 RingCT/type: yes/0
Extra: 01332f9e035574ccd5efa5bf3d2ccf50128659a819fb7646d3d57179f5b80078c202110000000775e3f0e9000000000000000000

1 output(s) for total of 0.695623040000 dcy

stealth address amount amount idx
00: d1c69ef4087896870360a59e1050a738034855662b5c14b7deff2d502c9ab3af 0.695623040000 1344969 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": 889010, "vin": [ { "gen": { "height": 889000 } } ], "vout": [ { "amount": 695623040, "target": { "key": "d1c69ef4087896870360a59e1050a738034855662b5c14b7deff2d502c9ab3af" } } ], "extra": [ 1, 51, 47, 158, 3, 85, 116, 204, 213, 239, 165, 191, 61, 44, 207, 80, 18, 134, 89, 168, 25, 251, 118, 70, 211, 213, 113, 121, 245, 184, 0, 120, 194, 2, 17, 0, 0, 0, 7, 117, 227, 240, 233, 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