Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 26599b395be48168a43a19b9336850b60bee545189a93f386753d78752c38999

Tx prefix hash: 58f2fa2f4205cd0ee2f600cbc716554bda20aba66fe9dc9998c85b3c594a198e
Tx public key: 37f76e2acb132b8f53cd1dd9df89c2aed96fc99870c3f1d3a8a1d24f13614d44
Timestamp: 1617578094 Timestamp [UCT]: 2021-04-04 23:14:54 Age [y:d:h:m:s]: 03:215:20:20:38
Block: 233350 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 913943 RingCT/type: yes/0
Extra: 0137f76e2acb132b8f53cd1dd9df89c2aed96fc99870c3f1d3a8a1d24f13614d440211000000109c1fbdcc000000000000000000

1 output(s) for total of 103.470169016000 dcy

stealth address amount amount idx
00: 090e7ad9cbf0142b0ae4055cb60554eabc53e418512284f4163dedb5ac9ee641 103.470169016000 484614 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": 233360, "vin": [ { "gen": { "height": 233350 } } ], "vout": [ { "amount": 103470169016, "target": { "key": "090e7ad9cbf0142b0ae4055cb60554eabc53e418512284f4163dedb5ac9ee641" } } ], "extra": [ 1, 55, 247, 110, 42, 203, 19, 43, 143, 83, 205, 29, 217, 223, 137, 194, 174, 217, 111, 201, 152, 112, 195, 241, 211, 168, 161, 210, 79, 19, 97, 77, 68, 2, 17, 0, 0, 0, 16, 156, 31, 189, 204, 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