Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 95836c0928ac3577c47d2a8e8424a3757aad2fa0a373305189c901425b2536ec

Tx prefix hash: 56436cd4c4a49b6567debd3f0cf4a84a4835c6504fbb0c66b6d7dfe4be6b03e8
Tx public key: 4932fddaafca82e7c52b89abf7de2a51ed5d7254054a5ddf630c84f9920003e3
Timestamp: 1705755200 Timestamp [UCT]: 2024-01-20 12:53:20 Age [y:d:h:m:s]: 00:347:01:20:22
Block: 939425 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 248503 RingCT/type: yes/0
Extra: 014932fddaafca82e7c52b89abf7de2a51ed5d7254054a5ddf630c84f9920003e302110000000d59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0f947a7b4f0504933aeb5ce4c6b1730d1dbb8e07a48dfcbc45cbdfe8530f05e7 0.600000000000 1397533 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": 939435, "vin": [ { "gen": { "height": 939425 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0f947a7b4f0504933aeb5ce4c6b1730d1dbb8e07a48dfcbc45cbdfe8530f05e7" } } ], "extra": [ 1, 73, 50, 253, 218, 175, 202, 130, 231, 197, 43, 137, 171, 247, 222, 42, 81, 237, 93, 114, 84, 5, 74, 93, 223, 99, 12, 132, 249, 146, 0, 3, 227, 2, 17, 0, 0, 0, 13, 89, 218, 211, 245, 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