← previous blocknext block →recent activity
Analyzing
Block #100,610,362
23 transactions · 17 stateful · 2026-08-31 00:15:49 UTC
Parallelism
91/100
Blocked
24%
Avg conflicts / tx
0.22
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #100,610,362 · 23 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
3w08w09w110w114w016w120w021w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x49b0842d…0a93
0x34b655…2a6f
4 touches
1 conflict
0x7f6d306a…876d
0x34b655…2a6f
4 touches
1 conflict
0x83f3d320…fb59
0x34b655…2a6f
4 touches
1 conflict
0xa242e227…2e45
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xafdec314…d06e
0x34b655…2a6f
4 touches
1 conflict
0xb482658a…e4f5
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
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 0x49b0842d79…d10a93
Audit this contract →
← previous block·next block →recent activity