Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 965e1bbe814891218a56acad1abd3b10a80f52f3a1cbfb020bda9359d904304e

Tx prefix hash: 93328f152c0f271493cd667b8ec0f5da9ab946e5202a6a9a93b4c239d3bf027f
Tx public key: a1913dd66d1cbb27193f9408cb176ab5dac7e877215c04a4d1f212039f285f80
Timestamp: 1643220580 Timestamp [UCT]: 2022-01-26 18:09:40 Age [y:d:h:m:s]: 03:279:04:17:31
Block: 425826 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 976398 RingCT/type: yes/0
Extra: 01a1913dd66d1cbb27193f9408cb176ab5dac7e877215c04a4d1f212039f285f80021100000001f1757e72000000000000000000

1 output(s) for total of 23.826596348000 dcy

stealth address amount amount idx
00: d747bc5bbb739cacc98ec15047d4581929f4004ce4d3be0028c18ea50de79d73 23.826596348000 834547 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": 425836, "vin": [ { "gen": { "height": 425826 } } ], "vout": [ { "amount": 23826596348, "target": { "key": "d747bc5bbb739cacc98ec15047d4581929f4004ce4d3be0028c18ea50de79d73" } } ], "extra": [ 1, 161, 145, 61, 214, 109, 28, 187, 39, 25, 63, 148, 8, 203, 23, 106, 181, 218, 199, 232, 119, 33, 92, 4, 164, 209, 242, 18, 3, 159, 40, 95, 128, 2, 17, 0, 0, 0, 1, 241, 117, 126, 114, 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