Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 431be7521be7d43b31dca22f697828de8cd346e1cd2f776bae11531338914ade

Tx prefix hash: c348bf2002cc216f2a742d7036d3b02e72353c18c7b94eff4f89b5067502a096
Tx public key: b17b6e51bdb65f62f7e591768e16ea85a8f5b5f651f0ed953f8a8afb76ca7ef4
Timestamp: 1737620936 Timestamp [UCT]: 2025-01-23 08:28:56 Age [y:d:h:m:s]: 00:146:05:53:32
Block: 1203448 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 104251 RingCT/type: yes/0
Extra: 01b17b6e51bdb65f62f7e591768e16ea85a8f5b5f651f0ed953f8a8afb76ca7ef4021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 20959f8e7255236991fce3eac2b147ac9b4c2fe245445855cd54ef32b9d2b82b 0.600000000000 1690125 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": 1203458, "vin": [ { "gen": { "height": 1203448 } } ], "vout": [ { "amount": 600000000, "target": { "key": "20959f8e7255236991fce3eac2b147ac9b4c2fe245445855cd54ef32b9d2b82b" } } ], "extra": [ 1, 177, 123, 110, 81, 189, 182, 95, 98, 247, 229, 145, 118, 142, 22, 234, 133, 168, 245, 181, 246, 81, 240, 237, 149, 63, 138, 138, 251, 118, 202, 126, 244, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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