Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 653a032c5b6a0b5c93ae0035b22a73b9410f688e3aa3e2eaabf199fbed82ad06

Tx prefix hash: 38d7984482367c3195ac93057cd2ea2a7ae0958bc2582bf49b81e5122e73d7c1
Tx public key: ad75d885a3632392580c1a8060b0e6ecf3d8db2a79ca213731401ed038449c7f
Timestamp: 1583240562 Timestamp [UCT]: 2020-03-03 13:02:42 Age [y:d:h:m:s]: 04:297:16:12:34
Block: 75847 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1106809 RingCT/type: yes/0
Extra: 01ad75d885a3632392580c1a8060b0e6ecf3d8db2a79ca213731401ed038449c7f0211000000134943cd9f000000000000000000

1 output(s) for total of 344.102794382000 dcy

stealth address amount amount idx
00: d8d840dff9b2d8a7a9a3462c869a2f8b91a5f46c22ac16e5953c62ab221c4014 344.102794382000 139826 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": 75857, "vin": [ { "gen": { "height": 75847 } } ], "vout": [ { "amount": 344102794382, "target": { "key": "d8d840dff9b2d8a7a9a3462c869a2f8b91a5f46c22ac16e5953c62ab221c4014" } } ], "extra": [ 1, 173, 117, 216, 133, 163, 99, 35, 146, 88, 12, 26, 128, 96, 176, 230, 236, 243, 216, 219, 42, 121, 202, 33, 55, 49, 64, 30, 208, 56, 68, 156, 127, 2, 17, 0, 0, 0, 19, 73, 67, 205, 159, 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