Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bb7353edee3bb53731f39d1ceb98ca3e9e54a905a04679b69266799b094f6912

Tx prefix hash: ad7f7543f1f6047e08f00b77d972cd7afcb3a3ba5bc1434098a15b6fade6eda9
Tx public key: 371bc5b9776030f489e3d855005b1b694879d8b5d6cb19e8566976eec76c92e7
Timestamp: 1722268564 Timestamp [UCT]: 2024-07-29 15:56:04 Age [y:d:h:m:s]: 00:298:04:56:32
Block: 1076357 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 213076 RingCT/type: yes/0
Extra: 01371bc5b9776030f489e3d855005b1b694879d8b5d6cb19e8566976eec76c92e702110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3f0071216ac36bbb2b92fb1b9b7d29982eeac16d1a93cc474dd61559d693248b 0.600000000000 1548894 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": 1076367, "vin": [ { "gen": { "height": 1076357 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3f0071216ac36bbb2b92fb1b9b7d29982eeac16d1a93cc474dd61559d693248b" } } ], "extra": [ 1, 55, 27, 197, 185, 119, 96, 48, 244, 137, 227, 216, 85, 0, 91, 27, 105, 72, 121, 216, 181, 214, 203, 25, 232, 86, 105, 118, 238, 199, 108, 146, 231, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 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