Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4226aa24cbf2fdda70f5486088f0f1eecabc6caf7e2e5aff1d5b3e1ce7ac2b85

Tx prefix hash: 9b3300f6462936f017b2dbcd18ecf3f3a7f1df563107223cba222f345a8bc12c
Tx public key: bc4ce826be6719e4b52445387974bec1e9894d932de84cacc4f82eb8a37cdb88
Timestamp: 1701076758 Timestamp [UCT]: 2023-11-27 09:19:18 Age [y:d:h:m:s]: 01:052:20:40:20
Block: 900669 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 299168 RingCT/type: yes/0
Extra: 01bc4ce826be6719e4b52445387974bec1e9894d932de84cacc4f82eb8a37cdb8802110000000633af99f4000000000000000000

1 output(s) for total of 0.636370003000 dcy

stealth address amount amount idx
00: 1f1e114389fa76a60f79c0b9a1c4f3073d4928418d8526ea18a9d7a2f68b22ca 0.636370003000 1357180 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": 900679, "vin": [ { "gen": { "height": 900669 } } ], "vout": [ { "amount": 636370003, "target": { "key": "1f1e114389fa76a60f79c0b9a1c4f3073d4928418d8526ea18a9d7a2f68b22ca" } } ], "extra": [ 1, 188, 76, 232, 38, 190, 103, 25, 228, 181, 36, 69, 56, 121, 116, 190, 193, 233, 137, 77, 147, 45, 232, 76, 172, 196, 248, 46, 184, 163, 124, 219, 136, 2, 17, 0, 0, 0, 6, 51, 175, 153, 244, 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