← previous blocknext block →recent activity
Analyzing
Block #94,491,003
18 transactions · 18 stateful · 2026-08-09 12:37:21 UTC
Parallelism
89/100
Blocked
17%
Avg conflicts / tx
0.22
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #94,491,003 · 18 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
2w05w06w18w09w110w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x206ed0b7…7ee9
0x34b655…2a6f
4 touches
1 conflict
0x34a1ee7e…fb20
0x34b655…2a6f
4 touches
1 conflict
0x3797ee05…071c
0x34b655…2a6f
4 touches
1 conflict
0x4b76146e…0dcb
0x34b655…2a6f
4 touches
1 conflict
0x66bdb4c2…7ea6
0x34b655…2a6f
4 touches
1 conflict
0x6d1b72ee…6b78
0x34b655…2a6f
4 touches
1 conflict
0x6f095f4f…918b
0x34b655…2a6f
4 touches
1 conflict
0x74f95963…01a2
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 0x206ed0b715…2c7ee9
Audit this contract →
← previous block·next block →recent activity