← previous blocknext block →recent activity
Analyzing
Block #100,737,730
15 transactions · 13 stateful · 2026-08-31 10:56:31 UTC
Parallelism
87/100
Blocked
23%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #100,737,730 · 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
6w07w19w010w113w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x41c56387…a8f6
0x34b655…2a6f
4 touches
1 conflict
0x42041fec…bd86
0x754704…b603
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x272b9268…c528
0x34b655…2a6f
4 touches
1 conflict
0x0c7deec4…77cb
0x34b655…2a6f
2 touches
0 conflicts
0x30a112bd…9e41
0x34b655…2a6f
2 touches
0 conflicts
0x63726607…4e47
0x34b655…2a6f
2 touches
0 conflicts
0x70e677f5…e3bd
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 0x41c5638713…86a8f6
Audit this contract →
← previous block·next block →recent activity