Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8f1cf24def8e9547fcb346aa9eec918438dcb1fba642bf0e8a9eed2048307509

Tx prefix hash: 2bb45001a960b40ea3b19443f8a4b1e8c0171f45249f50083d915c8c3ddde916
Tx public key: 012c88244ed5831dc5748bc2086a042cacd1ce9047673fe20d131021c001f19c
Timestamp: 1581249870 Timestamp [UCT]: 2020-02-09 12:04:30 Age [y:d:h:m:s]: 04:340:19:52:19
Block: 61346 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1135686 RingCT/type: yes/0
Extra: 01012c88244ed5831dc5748bc2086a042cacd1ce9047673fe20d131021c001f19c02110000000a4943cd9f000000000000000000

1 output(s) for total of 384.364762883000 dcy

stealth address amount amount idx
00: f6e5cfd784f30200a65aed3e91e4542c7913ff1a13d91adb647773bc7242c439 384.364762883000 113042 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": 61356, "vin": [ { "gen": { "height": 61346 } } ], "vout": [ { "amount": 384364762883, "target": { "key": "f6e5cfd784f30200a65aed3e91e4542c7913ff1a13d91adb647773bc7242c439" } } ], "extra": [ 1, 1, 44, 136, 36, 78, 213, 131, 29, 197, 116, 139, 194, 8, 106, 4, 44, 172, 209, 206, 144, 71, 103, 63, 226, 13, 19, 16, 33, 192, 1, 241, 156, 2, 17, 0, 0, 0, 10, 73, 67, 205, 159, 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