Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 366df5284959c4b6e8f5b0ee2952d224501f57394c531faf14e79ae8c1a29231

Tx prefix hash: bca019f75c002b35f10c90ed69433914f979fe99a85f596a899b7ba28bd71fc0
Tx public key: b875c16409c89402658137d8c4ab2cec626e68a996122f2ee076bd4cff8c390b
Timestamp: 1714813674 Timestamp [UCT]: 2024-05-04 09:07:54 Age [y:d:h:m:s]: 00:340:11:17:35
Block: 1014566 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 243360 RingCT/type: yes/0
Extra: 01b875c16409c89402658137d8c4ab2cec626e68a996122f2ee076bd4cff8c390b0211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 888d9115faa414d721d4311596f8ce6c901a3b3a24c7f66b0cb036900dac2c01 0.600000000000 1477691 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": 1014576, "vin": [ { "gen": { "height": 1014566 } } ], "vout": [ { "amount": 600000000, "target": { "key": "888d9115faa414d721d4311596f8ce6c901a3b3a24c7f66b0cb036900dac2c01" } } ], "extra": [ 1, 184, 117, 193, 100, 9, 200, 148, 2, 101, 129, 55, 216, 196, 171, 44, 236, 98, 110, 104, 169, 150, 18, 47, 46, 224, 118, 189, 76, 255, 140, 57, 11, 2, 17, 0, 0, 0, 5, 122, 156, 244, 199, 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