Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a85674c3e4ed9851ab64940a96de22393c3ebf60ed4684d01483de139c25408c

Tx prefix hash: 6158345a0253a3ae881f6d3fa3c13f107bd3b0839eaa28fd52c51418b318857a
Tx public key: 10b92f599e4ee085be94caa46343e627adb5746c44443080d23a3e2de0040190
Timestamp: 1699713112 Timestamp [UCT]: 2023-11-11 14:31:52 Age [y:d:h:m:s]: 01:202:12:55:02
Block: 889363 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 405986 RingCT/type: yes/0
Extra: 0110b92f599e4ee085be94caa46343e627adb5746c44443080d23a3e2de004019002110000000633af99f4000000000000000000

1 output(s) for total of 0.693699191000 dcy

stealth address amount amount idx
00: a8fec01991b262ef9cbc1807b7b7fdb0a400f1c16c24343166c2ecc3c6c64672 0.693699191000 1345358 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": 889373, "vin": [ { "gen": { "height": 889363 } } ], "vout": [ { "amount": 693699191, "target": { "key": "a8fec01991b262ef9cbc1807b7b7fdb0a400f1c16c24343166c2ecc3c6c64672" } } ], "extra": [ 1, 16, 185, 47, 89, 158, 78, 224, 133, 190, 148, 202, 164, 99, 67, 230, 39, 173, 181, 116, 108, 68, 68, 48, 128, 210, 58, 62, 45, 224, 4, 1, 144, 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