← previous blocknext block →recent activity
Analyzing
Block #100,136,813
14 transactions · 13 stateful · 2026-08-29 08:29:17 UTC
Parallelism
79/100
Blocked
46%
Avg conflicts / tx
0.5
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,136,813 · 14 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
1w02w03w14w16w08w19w211w213w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xde8204f8…8615
0x34b655…2a6f
4 touches
1 conflict
0x1d9154e7…8821
0x34b655…2a6f
4 touches
1 conflict
0x50c61506…343f
0x34b655…2a6f
4 touches
1 conflict
0x5e07769b…a192
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0xa11b60f7…8e8b
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
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
1 conflict on slot 0xde8204f883…7e8615
Audit this contract →
← previous block·next block →recent activity