Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 311c5e20d22ac139e416a1f07d773cf0fe12046a1475322247370cae3f6a789f

Tx prefix hash: 1c50fd2944c2389fd2a5a4ee6f6e90eff88ec4c13ba60eee0fc46bf8074f5354
Tx public key: 9a06243b9dc8773010cb48e51d05cd2d21736259b0d3c9c7222644f5500d6284
Timestamp: 1650614870 Timestamp [UCT]: 2022-04-22 08:07:50 Age [y:d:h:m:s]: 02:165:23:16:03
Block: 485550 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 638559 RingCT/type: yes/0
Extra: 019a06243b9dc8773010cb48e51d05cd2d21736259b0d3c9c7222644f5500d6284021100000002c9067537000000000000000000

1 output(s) for total of 15.106766457000 dcy

stealth address amount amount idx
00: 7240117a8b55328893e957c9cca82a6f77f1036989cbcd27bc0ced7748d219aa 15.106766457000 907651 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": 485560, "vin": [ { "gen": { "height": 485550 } } ], "vout": [ { "amount": 15106766457, "target": { "key": "7240117a8b55328893e957c9cca82a6f77f1036989cbcd27bc0ced7748d219aa" } } ], "extra": [ 1, 154, 6, 36, 59, 157, 200, 119, 48, 16, 203, 72, 229, 29, 5, 205, 45, 33, 115, 98, 89, 176, 211, 201, 199, 34, 38, 68, 245, 80, 13, 98, 132, 2, 17, 0, 0, 0, 2, 201, 6, 117, 55, 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