Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4da593beee4f4e5a2bcb9068dd94e0e6a5f1c6379360ec6f5dc0fe599b809ea8

Tx prefix hash: 8ea89e31a1e067c6d160b48db3065f5a70958680688b791f5bf86a228dfd3163
Tx public key: 121c6092c46190f727bef6f8ec54cda7f835d81a6b348f3a44b2f8ca9b9b28ed
Timestamp: 1700368122 Timestamp [UCT]: 2023-11-19 04:28:42 Age [y:d:h:m:s]: 01:097:09:49:00
Block: 894791 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 330757 RingCT/type: yes/0
Extra: 01121c6092c46190f727bef6f8ec54cda7f835d81a6b348f3a44b2f8ca9b9b28ed02110000000275e3f0e9000000000000000000

1 output(s) for total of 0.665558084000 dcy

stealth address amount amount idx
00: aa9f589b1f9032aea27126f4f7f8d9d37ca46920fb81dbeade754184551117bb 0.665558084000 1351002 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": 894801, "vin": [ { "gen": { "height": 894791 } } ], "vout": [ { "amount": 665558084, "target": { "key": "aa9f589b1f9032aea27126f4f7f8d9d37ca46920fb81dbeade754184551117bb" } } ], "extra": [ 1, 18, 28, 96, 146, 196, 97, 144, 247, 39, 190, 246, 248, 236, 84, 205, 167, 248, 53, 216, 26, 107, 52, 143, 58, 68, 178, 248, 202, 155, 155, 40, 237, 2, 17, 0, 0, 0, 2, 117, 227, 240, 233, 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