Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3ee775c37307b7a681762bb792a72dc967885da04a770ecc2ccb6df28f256ca1

Tx prefix hash: 88b3571b6fd5cc248d6b00375812ba8220f3e9c1a22133ad01068e3e19acc7d5
Tx public key: af02b709418910a221aeb4d91c34ae1e98d40952b6a7f08193d26dd75b38d130
Timestamp: 1745198522 Timestamp [UCT]: 2025-04-21 01:22:02 Age [y:d:h:m:s]: 00:199:04:33:37
Block: 1265937 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 140075 RingCT/type: yes/0
Extra: 01af02b709418910a221aeb4d91c34ae1e98d40952b6a7f08193d26dd75b38d1300211000000036c98aa3d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8bd57a0bf032110528680d85b0c448599c26ab9b67b8bcb40d0b4de91dd34f0f 0.600000000000 1753150 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": 1265947, "vin": [ { "gen": { "height": 1265937 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8bd57a0bf032110528680d85b0c448599c26ab9b67b8bcb40d0b4de91dd34f0f" } } ], "extra": [ 1, 175, 2, 183, 9, 65, 137, 16, 162, 33, 174, 180, 217, 28, 52, 174, 30, 152, 212, 9, 82, 182, 167, 240, 129, 147, 210, 109, 215, 91, 56, 209, 48, 2, 17, 0, 0, 0, 3, 108, 152, 170, 61, 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