Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1002af5f920fe492a4195ff287b9a918b47145c5e78b3db1b7b6eddda5186f1f

Tx prefix hash: fb61b017c1185e6f631e2634f84b173ab6956dada4a797393dac73f6b7f30433
Tx public key: e5e53b25042aa36b49cf686dc14e55dffd3ef596af83f01bdaa84dd23281c5a5
Timestamp: 1720387029 Timestamp [UCT]: 2024-07-07 21:17:09 Age [y:d:h:m:s]: 00:199:16:10:36
Block: 1060765 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 142831 RingCT/type: yes/0
Extra: 01e5e53b25042aa36b49cf686dc14e55dffd3ef596af83f01bdaa84dd23281c5a502110000000ce914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c7f3dd90e46237ef8c4f3b5c2339e71e11b37f19b99daf775d0d986cd38279be 0.600000000000 1531250 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": 1060775, "vin": [ { "gen": { "height": 1060765 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c7f3dd90e46237ef8c4f3b5c2339e71e11b37f19b99daf775d0d986cd38279be" } } ], "extra": [ 1, 229, 229, 59, 37, 4, 42, 163, 107, 73, 207, 104, 109, 193, 78, 85, 223, 253, 62, 245, 150, 175, 131, 240, 27, 218, 168, 77, 210, 50, 129, 197, 165, 2, 17, 0, 0, 0, 12, 233, 20, 221, 21, 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