Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9b7bd19c45cb5fe0cc244d993b4ca1b468372d8038e524d80911236ab7815118

Tx prefix hash: c9648027f88d2a4e868464c0c34523413f1c32a85ad1acd54753bcea88721578
Tx public key: 8f56ba79aaf78fbb9ad4e861dd87fb40f2898d3c799a282b6a9c78f9cc4b3372
Timestamp: 1710584858 Timestamp [UCT]: 2024-03-16 10:27:38 Age [y:d:h:m:s]: 01:009:06:10:00
Block: 979517 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 267571 RingCT/type: yes/0
Extra: 018f56ba79aaf78fbb9ad4e861dd87fb40f2898d3c799a282b6a9c78f9cc4b337202110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3d8216ba1488909226db5f5759a4d985e932ccbe39a042cb82ce87e639f24cc7 0.600000000000 1439552 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": 979527, "vin": [ { "gen": { "height": 979517 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3d8216ba1488909226db5f5759a4d985e932ccbe39a042cb82ce87e639f24cc7" } } ], "extra": [ 1, 143, 86, 186, 121, 170, 247, 143, 187, 154, 212, 232, 97, 221, 135, 251, 64, 242, 137, 141, 60, 121, 154, 40, 43, 106, 156, 120, 249, 204, 75, 51, 114, 2, 17, 0, 0, 0, 4, 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