Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f13f103fc9a8228e1e25b44f574c7a23c54146f44ae27c4fa103ad495ea0f137

Tx prefix hash: d50cc3c39c99c1a37ab359f59bbe716c8dc73166a49aea1a4bcd13a96b9bdbcc
Tx public key: 98173021fdf85860f2a2507dbacaf3bda0f7e30bdb4a2210bd4b9a1195ad1ade
Timestamp: 1658475961 Timestamp [UCT]: 2022-07-22 07:46:01 Age [y:d:h:m:s]: 02:207:07:27:17
Block: 549130 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 669325 RingCT/type: yes/0
Extra: 0198173021fdf85860f2a2507dbacaf3bda0f7e30bdb4a2210bd4b9a1195ad1ade0211000000114da16a3a000000000000000000

1 output(s) for total of 9.300461276000 dcy

stealth address amount amount idx
00: a6a02dd8300626b50b7a4656085b82e5b8e106b63cd7046b09ee96534299bdfa 9.300461276000 980463 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": 549140, "vin": [ { "gen": { "height": 549130 } } ], "vout": [ { "amount": 9300461276, "target": { "key": "a6a02dd8300626b50b7a4656085b82e5b8e106b63cd7046b09ee96534299bdfa" } } ], "extra": [ 1, 152, 23, 48, 33, 253, 248, 88, 96, 242, 162, 80, 125, 186, 202, 243, 189, 160, 247, 227, 11, 219, 74, 34, 16, 189, 75, 154, 17, 149, 173, 26, 222, 2, 17, 0, 0, 0, 17, 77, 161, 106, 58, 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