Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2f506a7a3b926fd8fa08397ac91f75c2046388de6c8cf4fc2483234ff6c07ed3

Tx prefix hash: dd51fd88b0341a52a9873c6dc66980e130d3c2b24e3c9fa33ae725489a961ed0
Tx public key: c27d6ce2c7cf8aeb93f38f416ea081b579ffce94eee66d08d8acd2cf5a19f8b9
Timestamp: 1679430693 Timestamp [UCT]: 2023-03-21 20:31:33 Age [y:d:h:m:s]: 01:343:06:45:29
Block: 722115 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 505974 RingCT/type: yes/0
Extra: 01c27d6ce2c7cf8aeb93f38f416ea081b579ffce94eee66d08d8acd2cf5a19f8b90211000000035029cbac000000000000000000

1 output(s) for total of 2.485038501000 dcy

stealth address amount amount idx
00: a6a037d91a38be21c80df240ac4f8fe7fcdc6c302ae12643bfa77f7c71e5641e 2.485038501000 1167024 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": 722125, "vin": [ { "gen": { "height": 722115 } } ], "vout": [ { "amount": 2485038501, "target": { "key": "a6a037d91a38be21c80df240ac4f8fe7fcdc6c302ae12643bfa77f7c71e5641e" } } ], "extra": [ 1, 194, 125, 108, 226, 199, 207, 138, 235, 147, 243, 143, 65, 110, 160, 129, 181, 121, 255, 206, 148, 238, 230, 109, 8, 216, 172, 210, 207, 90, 25, 248, 185, 2, 17, 0, 0, 0, 3, 80, 41, 203, 172, 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