← previous blocknext block →recent activity
Analyzing
Block #100,633,540
19 transactions · 14 stateful · 2026-08-31 02:12:25 UTC
Parallelism
74/100
Blocked
50%
Avg conflicts / tx
0.58
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #100,633,540 · 19 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w16w07w18w29w310w311w416w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x49890ced…6f23
0x34b655…2a6f
6 touches
3 conflicts
0xfe39a1f7…8eb0
0x34b655…2a6f
6 touches
3 conflicts
0xe9457301…83cd
0x34b655…2a6f
6 touches
3 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0xe3d7c1f1…1f50
0x34b655…2a6f
6 touches
3 conflicts
0xa1382963…84c6
0x34b655…2a6f
6 touches
3 conflicts
0x5684aadd…8d62
0x34b655…2a6f
4 touches
1 conflict
0x177da55c…fe82
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
3 conflicts on slot 0x49890ced8d…316f23
Audit this contract →
← previous block·next block →recent activity