Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6aaee4bebf3e0285041d42020094732269b5bb1281e8bafe359d388f070d5926

Tx prefix hash: bd6961f36e68e46b8bce5f11759c3307b4b46b04271674884912121386681880
Tx public key: 65461bed32e8ed4a93b3e67e53b99cd8bc9fbf4c0a21a786e379e2b4bafeaec8
Timestamp: 1726540051 Timestamp [UCT]: 2024-09-17 02:27:31 Age [y:d:h:m:s]: 00:197:15:58:54
Block: 1111771 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 141099 RingCT/type: yes/0
Extra: 0165461bed32e8ed4a93b3e67e53b99cd8bc9fbf4c0a21a786e379e2b4bafeaec802110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: afdcb5f03445b66c8002b8fb9d545f527d2827bb9c8961f525bf327c05e2d5bf 0.600000000000 1590848 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": 1111781, "vin": [ { "gen": { "height": 1111771 } } ], "vout": [ { "amount": 600000000, "target": { "key": "afdcb5f03445b66c8002b8fb9d545f527d2827bb9c8961f525bf327c05e2d5bf" } } ], "extra": [ 1, 101, 70, 27, 237, 50, 232, 237, 74, 147, 179, 230, 126, 83, 185, 156, 216, 188, 159, 191, 76, 10, 33, 167, 134, 227, 121, 226, 180, 186, 254, 174, 200, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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