Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 667b804437853a943f4095cb46e80ff4c1fb9ee4394b883f8c4f3631af0fb7ec

Tx prefix hash: 7a1ca0abc07f61fc7d6dd8e94562dbf1bd73a9cdebc93b3cda9cb14119f36e9e
Tx public key: d291f27de0c03769ec816070e882ab8e7ccd849c72d6d3b35281cce59a83bd2a
Timestamp: 1696885437 Timestamp [UCT]: 2023-10-09 21:03:57 Age [y:d:h:m:s]: 01:141:18:19:54
Block: 866131 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 362322 RingCT/type: yes/0
Extra: 01d291f27de0c03769ec816070e882ab8e7ccd849c72d6d3b35281cce59a83bd2a02110000000675e3f0e9000000000000000000

1 output(s) for total of 0.828225279000 dcy

stealth address amount amount idx
00: cca09adfa28deab6207ce471e42aaca2cda02a46f0e8f0b162a4cddb9ae328c1 0.828225279000 1320703 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": 866141, "vin": [ { "gen": { "height": 866131 } } ], "vout": [ { "amount": 828225279, "target": { "key": "cca09adfa28deab6207ce471e42aaca2cda02a46f0e8f0b162a4cddb9ae328c1" } } ], "extra": [ 1, 210, 145, 242, 125, 224, 192, 55, 105, 236, 129, 96, 112, 232, 130, 171, 142, 124, 205, 132, 156, 114, 214, 211, 179, 82, 129, 204, 229, 154, 131, 189, 42, 2, 17, 0, 0, 0, 6, 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