← previous blocknext block →recent activity
Analyzing
Block #100,054,502
10 transactions · 10 stateful · 2026-08-29 01:34:44 UTC
Parallelism
80/100
Blocked
20%
Avg conflicts / tx
0.3
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #100,054,502 · 10 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w07w18w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2ad2f4bc…1800
0x34b655…2a6f
4 touches
1 conflict
0x08d66073…e706
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35d
0x34b655…2a6f
4 touches
1 conflict
0x5492de24…e2e8
0x34b655…2a6f
3 touches
1 conflict
0x8666a375…c417
0x34b655…2a6f
2 touches
0 conflicts
0xc897f6e3…4803
0x34b655…2a6f
2 touches
0 conflicts
0xca5b9231…3bd1
0x34b655…2a6f
2 touches
0 conflicts
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
1 conflict on slot 0x2ad2f4bc01…9d1800
Audit this contract →
← previous block·next block →recent activity