← previous blocknext block →recent activity
Analyzing
Block #100,856,866
15 transactions · 15 stateful · 2026-08-31 20:56:14 UTC
Parallelism
87/100
Blocked
13%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #100,856,866 · 15 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
1w02w17w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xebcb0f2d…9305
0x34b655…2a6f
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x089e53c0…6466
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0x50e84e6c…287f
0x34b655…2a6f
2 touches
0 conflicts
0x6f4e7625…aba5
0x34b655…2a6f
2 touches
0 conflicts
0x775a8ad3…8307
0x34b655…2a6f
2 touches
0 conflicts
0x8b87ece6…3353
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 0xebcb0f2dca…da9305
Audit this contract →
← previous block·next block →recent activity