Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e421db43691ba027e8f2dda0435a9b59d91085cc5a9ce4b9fdae7d4bb81bc89d

Tx prefix hash: d1a2293eac276c41c110fc887dcc6f0318748a8450875675c2e64d4507c3a847
Tx public key: 556fd56a793042a65d129df2a7379e2a9ae538c746dbbf68f80c35f9cca3886a
Timestamp: 1712920199 Timestamp [UCT]: 2024-04-12 11:09:59 Age [y:d:h:m:s]: 00:319:01:07:58
Block: 998839 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 228084 RingCT/type: yes/0
Extra: 01556fd56a793042a65d129df2a7379e2a9ae538c746dbbf68f80c35f9cca3886a02110000000452d47e94000000000000000000

1 output(s) for total of 0.600070000000 dcy

stealth address amount amount idx
00: 532989e361126bead0ddc97608ad6ca824ab459e69f555d9b7b252b86368e422 0.600070000000 1459303 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": 998849, "vin": [ { "gen": { "height": 998839 } } ], "vout": [ { "amount": 600070000, "target": { "key": "532989e361126bead0ddc97608ad6ca824ab459e69f555d9b7b252b86368e422" } } ], "extra": [ 1, 85, 111, 213, 106, 121, 48, 66, 166, 93, 18, 157, 242, 167, 55, 158, 42, 154, 229, 56, 199, 70, 219, 191, 104, 248, 12, 53, 249, 204, 163, 136, 106, 2, 17, 0, 0, 0, 4, 82, 212, 126, 148, 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