← previous blocknext block →recent activity
Analyzing
Block #100,614,112
26 transactions · 21 stateful · 2026-08-31 00:34:41 UTC
Parallelism
85/100
Blocked
33%
Avg conflicts / tx
0.46
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #100,614,112 · 26 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
4w05w18w210w015w017w018w119w220w324w125w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe3abe489…ebf3
0x6eb2af…2f9a
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xe3abe489…ebf4
0x6eb2af…2f9a
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
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: 0x6eb2af5f…1a2f9a
6 conflicts on slot 0xe3abe4895e…e5ebf3
Audit this contract →
← previous block·next block →recent activity