Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e625686bfb81352265d113c8080f0562d7a14265c165506ae3b256c13d13643a

Tx prefix hash: ded6c82117a436304cdbce4d36888ff9808599c21141d764d1001e9b7a9ac08d
Tx public key: c5795abf8ef26e5fb68d61a7ee2ada635d8f0ea0ba8f873c3b90baa8ae36571d
Timestamp: 1706461247 Timestamp [UCT]: 2024-01-28 17:00:47 Age [y:d:h:m:s]: 01:288:16:27:50
Block: 945288 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 465132 RingCT/type: yes/0
Extra: 01c5795abf8ef26e5fb68d61a7ee2ada635d8f0ea0ba8f873c3b90baa8ae36571d02110000000759dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 73c77c49402418c2b30ab3d4040cc19d7a6964c7221380888a08d400d7651b46 0.600000000000 1403600 of 15

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": 945298, "vin": [ { "gen": { "height": 945288 } } ], "vout": [ { "amount": 600000000, "target": { "key": "73c77c49402418c2b30ab3d4040cc19d7a6964c7221380888a08d400d7651b46" } } ], "extra": [ 1, 197, 121, 90, 191, 142, 242, 110, 95, 182, 141, 97, 167, 238, 42, 218, 99, 93, 143, 14, 160, 186, 143, 135, 60, 59, 144, 186, 168, 174, 54, 87, 29, 2, 17, 0, 0, 0, 7, 89, 218, 211, 245, 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