← previous blocknext block →recent activity
Analyzing
Block #100,431,047
18 transactions · 16 stateful · 2026-08-30 09:13:39 UTC
Parallelism
83/100
Blocked
19%
Avg conflicts / tx
0.22
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,431,047 · 18 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w05w114w216w017w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcf37f77e…a027
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x6b624576…5a45
0x34b655…2a6f
4 touches
1 conflict
0x451e482b…7e7d
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
2 touches
0 conflicts
0x06e40499…165e
0x2b46c0…1669
2 touches
0 conflicts
0xa605468c…1bfc
0x2b46c0…1669
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 0xcf37f77e49…18a027
Audit this contract →
← previous block·next block →recent activity