Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 61a04f83c16dc477df8ac201ba0cd1fcd630828c0b344e978a93386a36b5ec9d

Tx prefix hash: d650566757f8baf1d0e2a6cf036c2285e99671ba550f6c62763928c64da7f23c
Tx public key: f96fcc3b7f66cbcfcef0c7ddac0580d1b28d0a6e42cbe3b9441acf606ca1f330
Timestamp: 1696714056 Timestamp [UCT]: 2023-10-07 21:27:36 Age [y:d:h:m:s]: 01:252:04:01:02
Block: 864708 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 441208 RingCT/type: yes/0
Extra: 01f96fcc3b7f66cbcfcef0c7ddac0580d1b28d0a6e42cbe3b9441acf606ca1f33002110000000175e3f0e9000000000000000000

1 output(s) for total of 0.837266035000 dcy

stealth address amount amount idx
00: a3f90eb9ec2ca18c80d15e1ecd03d4ea00ce848bd76b8f2c447ea167dc079a95 0.837266035000 1319228 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": 864718, "vin": [ { "gen": { "height": 864708 } } ], "vout": [ { "amount": 837266035, "target": { "key": "a3f90eb9ec2ca18c80d15e1ecd03d4ea00ce848bd76b8f2c447ea167dc079a95" } } ], "extra": [ 1, 249, 111, 204, 59, 127, 102, 203, 207, 206, 240, 199, 221, 172, 5, 128, 209, 178, 141, 10, 110, 66, 203, 227, 185, 68, 26, 207, 96, 108, 161, 243, 48, 2, 17, 0, 0, 0, 1, 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