← previous blocknext block →recent activity
Analyzing
Block #92,822,198
15 transactions · 13 stateful · 2026-08-03 16:27:21 UTC
Parallelism
87/100
Blocked
31%
Avg conflicts / tx
0.27
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #92,822,198 · 15 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
2w03w15w06w17w09w010w113w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0f2d78b1…7363
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0031
0x59df86…2780
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…0002
0x91855e…ac7e
4 touches
1 conflict
0x1bde9f7f…c070
0x34b655…2a6f
2 touches
0 conflicts
0x1cf8ee39…f10f
0x34b655…2a6f
2 touches
0 conflicts
0x1e166a45…98a7
0x34b655…2a6f
2 touches
0 conflicts
0x201cb196…27fa
0x34b655…2a6f
2 touches
0 conflicts
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 0x0f2d78b1bb…5e7363
Audit this contract →
← previous block·next block →recent activity