← previous blocknext block →recent activity
Analyzing
Block #93,063,890
24 transactions · 19 stateful · 2026-08-04 12:43:37 UTC
Parallelism
83/100
Blocked
47%
Avg conflicts / tx
0.63
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #93,063,890 · 24 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w07w08w19w211w012w113w214w316w118w019w120w322w023w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbd41f53e…2dc4
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0031
0x59df86…2780
6 touches
3 conflicts
0xa3a621f8…75a2
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x5814330e…08e9
0x34b655…2a6f
4 touches
1 conflict
0x5a65207b…4f30
0x34b655…2a6f
4 touches
1 conflict
0x5b37bb6b…aaff
0x34b655…2a6f
4 touches
1 conflict
0x5b37bb6b…ab00
0x34b655…2a6f
4 touches
1 conflict
What's blocking what?
Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.
The bottleneck
Throughput-killer: Perpl
6 conflicts on slot 0xbd41f53efd…fe2dc4
Audit this contract →
← previous block·next block →recent activity