Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 81270ad29e1ce1de4a36c36c9d70227f9ec85f91b750f38182443eba556a96e1

Tx prefix hash: b5e6c631bd1bccf4cc4584249d2601a72b1879ba990fbcfea6ce8c3091ca38da
Tx public key: 82d23ee1b4d6605d1ca3260e8d7b6627b97e00743cd71d7878fcb9863b5e0e52
Timestamp: 1738415297 Timestamp [UCT]: 2025-02-01 13:08:17 Age [y:d:h:m:s]: 00:292:14:55:44
Block: 1209794 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 206897 RingCT/type: yes/0
Extra: 0182d23ee1b4d6605d1ca3260e8d7b6627b97e00743cd71d7878fcb9863b5e0e5202110000000c1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0fdb710247eae3b3a2f14366513cf3629a2de3cc421ae1c65d0f69a9bd1aca02 0.600000000000 1696541 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": 1209804, "vin": [ { "gen": { "height": 1209794 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0fdb710247eae3b3a2f14366513cf3629a2de3cc421ae1c65d0f69a9bd1aca02" } } ], "extra": [ 1, 130, 210, 62, 225, 180, 214, 96, 93, 28, 163, 38, 14, 141, 123, 102, 39, 185, 126, 0, 116, 60, 215, 29, 120, 120, 252, 185, 134, 59, 94, 14, 82, 2, 17, 0, 0, 0, 12, 31, 10, 83, 235, 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