← previous blocknext block →recent activity
Analyzing
Block #100,162,839
16 transactions · 13 stateful · 2026-08-29 10:40:21 UTC
Parallelism
63/100
Blocked
46%
Avg conflicts / tx
0.94
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #100,162,839 · 16 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w18w29w310w411w012w114w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2871e914…0dc4
0x34b655…2a6f
8 touches
6 conflicts
0xd2a76d80…ee44
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xdd5a06f0…6ccd
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x0ed7cc0b…ee52
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35e
0x34b655…2a6f
4 touches
1 conflict
0x09106a95…1467
0x33176b…e078
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 0x2871e9147d…610dc4
Audit this contract →
← previous block·next block →recent activity