← previous blocknext block →recent activity
Analyzing
Block #100,618,700
22 transactions · 20 stateful · 2026-08-31 00:57:46 UTC
Parallelism
64/100
Blocked
55%
Avg conflicts / tx
0.86
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #100,618,700 · 22 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w16w07w08w19w110w211w312w313w415w418w519w621w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe2de1aea…8024
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xc578fee4…40b6
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0x35cc4d4e…1eff
0x34b655…2a6f
6 touches
3 conflicts
0x49890ced…6f23
0x34b655…2a6f
4 touches
1 conflict
0x6d105005…3cc9
0x34b655…2a6f
4 touches
1 conflict
0x74240bd4…0f39
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 0xe2de1aeae5…be8024
Audit this contract →
← previous block·next block →recent activity