Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3fd21b259f63e87ba892429bf42ea6568400e5af8ee6d90e72e43ced1f9a42c9

Tx prefix hash: d6a4b8cadca7496266ae5170b7b73b9c2a9324dc905a16dcd7e2d37531d402a1
Tx public key: adde3477fb9d56156524e379758103159636deeb6d4ba75ba6a0e17b5f309874
Timestamp: 1713283503 Timestamp [UCT]: 2024-04-16 16:05:03 Age [y:d:h:m:s]: 00:355:14:43:43
Block: 1001848 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 254250 RingCT/type: yes/0
Extra: 01adde3477fb9d56156524e379758103159636deeb6d4ba75ba6a0e17b5f3098740211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b11da29ae416d3a086c43bce50089b5e01f553b07a0bb43d1caac160e2bc1dfd 0.600000000000 1462360 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": 1001858, "vin": [ { "gen": { "height": 1001848 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b11da29ae416d3a086c43bce50089b5e01f553b07a0bb43d1caac160e2bc1dfd" } } ], "extra": [ 1, 173, 222, 52, 119, 251, 157, 86, 21, 101, 36, 227, 121, 117, 129, 3, 21, 150, 54, 222, 235, 109, 75, 167, 91, 166, 160, 225, 123, 95, 48, 152, 116, 2, 17, 0, 0, 0, 2, 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