Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d38f10f6f4fe11b69bc8be9530f42a62e9c7be0c0566732d16af86bdedc6a55b

Tx prefix hash: bdfcc900d1e0303dbcaa5cd80c4b22d8068d73d6079d5215cd5e57b556fdaba3
Tx public key: b16c39b01ebc9af46e51272a968ca17814f2befaec66f7b0d77d568901d620e5
Timestamp: 1716519126 Timestamp [UCT]: 2024-05-24 02:52:06 Age [y:d:h:m:s]: 00:160:21:51:32
Block: 1028709 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 115176 RingCT/type: yes/0
Extra: 01b16c39b01ebc9af46e51272a968ca17814f2befaec66f7b0d77d568901d620e502110000000652d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b375b0ec4837a2bcf7b281535ce6bf4805b3f70e25820d2eec0d272d82aa157d 0.600000000000 1496706 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": 1028719, "vin": [ { "gen": { "height": 1028709 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b375b0ec4837a2bcf7b281535ce6bf4805b3f70e25820d2eec0d272d82aa157d" } } ], "extra": [ 1, 177, 108, 57, 176, 30, 188, 154, 244, 110, 81, 39, 42, 150, 140, 161, 120, 20, 242, 190, 250, 236, 102, 247, 176, 215, 125, 86, 137, 1, 214, 32, 229, 2, 17, 0, 0, 0, 6, 82, 212, 126, 148, 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