Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8959bc03e121e46ee7bfe1aad847fffe6a59598f02ea6ae658c8779a6685700a

Tx prefix hash: 42a03a7357b36f2ea212ec5eaf3a9cbb21a6ac829faa9cc167d61e886c8e557a
Tx public key: a6731a929052a6dbf4c8bc60d64ae8f1843f2d397cfb28c549105410c18850a5
Timestamp: 1706854885 Timestamp [UCT]: 2024-02-02 06:21:25 Age [y:d:h:m:s]: 01:058:18:49:19
Block: 948570 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 303066 RingCT/type: yes/0
Extra: 01a6731a929052a6dbf4c8bc60d64ae8f1843f2d397cfb28c549105410c18850a502110000000759dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3ec3e0e7453facdbea7158e0e23b46246d12b8b5737aa803925052d369f5a33b 0.600000000000 1407004 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": 948580, "vin": [ { "gen": { "height": 948570 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3ec3e0e7453facdbea7158e0e23b46246d12b8b5737aa803925052d369f5a33b" } } ], "extra": [ 1, 166, 115, 26, 146, 144, 82, 166, 219, 244, 200, 188, 96, 214, 74, 232, 241, 132, 63, 45, 57, 124, 251, 40, 197, 73, 16, 84, 16, 193, 136, 80, 165, 2, 17, 0, 0, 0, 7, 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