← previous blocknext block →recent activity
Analyzing
Block #100,813,883
12 transactions · 12 stateful · 2026-08-31 17:19:48 UTC
Parallelism
75/100
Blocked
25%
Avg conflicts / tx
0.25
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,813,883 · 12 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
1w02w17w010w111w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x326a02b5…8dad
0x34b655…2a6f
4 touches
1 conflict
0x0cfb5d79…7ccc
0x2880ab…7b43
2 touches
0 conflicts
0x12117fd0…ec1a
0x2880ab…7b43
2 touches
0 conflicts
0xabde8104…c9a9
0x2a68ba…90c5
2 touches
0 conflicts
0xb05cd4f5…73d0
0x34ae4d…3fc5
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity