← previous blocknext block →recent activity
Analyzing
Block #100,924,082
18 transactions · 15 stateful · 2026-09-01 02:34:19 UTC
Parallelism
72/100
Blocked
27%
Avg conflicts / tx
0.44
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #100,924,082 · 18 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
8w09w110w211w317w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xebe581d8…2696
0x34b655…2a6f
8 touches
6 conflicts
0x9aed5849…2f7e
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x0c7103bd…4f89
0x34b655…2a6f
4 touches
1 conflict
0x12c00063…cb00
0x34b655…2a6f
4 touches
1 conflict
0x3dae5ee1…721b
0x34b655…2a6f
4 touches
1 conflict
0x42522e76…2592
0x34b655…2a6f
4 touches
1 conflict
0x9efa1eba…efbf
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 0xebe581d8e8…f12696
Audit this contract →
← previous block·next block →recent activity