← previous blocknext block →recent activity
Analyzing
Block #100,141,647
18 transactions · 12 stateful · 2026-08-29 08:53:37 UTC
Parallelism
83/100
Blocked
33%
Avg conflicts / tx
0.28
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,141,647 · 18 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
7w09w110w213w217w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbd3735d7…c973
0x34b655…2a6f
6 touches
3 conflicts
0xbbe823d1…efae
0x34b655…2a6f
6 touches
3 conflicts
0xe1c4e5ce…0dec
0x34b655…2a6f
6 touches
3 conflicts
0x191e0467…70e5
0x34b655…2a6f
4 touches
1 conflict
0x5cb2ad15…0483
0x34b655…2a6f
4 touches
1 conflict
0x03fe6234…08dd
0x34b655…2a6f
4 touches
1 conflict
0x03fe6234…08de
0x34b655…2a6f
4 touches
1 conflict
0x75f36d60…8556
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
3 conflicts on slot 0xbd3735d732…a9c973
Audit this contract →
← previous block·next block →recent activity