← previous blocknext block →recent activity
Analyzing
Block #101,992,193
13 transactions · 13 stateful · 2026-09-04 20:12:23 UTC
Parallelism
85/100
Blocked
15%
Avg conflicts / tx
0.31
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #101,992,193 · 13 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
1w03w04w16w09w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x767c56c7…ec85
0x34b655…2a6f
4 touches
1 conflict
0x2c84cfcc…351b
0x34b655…2a6f
4 touches
1 conflict
0x51fc8795…126f
0x34b655…2a6f
4 touches
1 conflict
0x8e10b110…c501
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0x2d2ef87a…d023
0x34b655…2a6f
2 touches
0 conflicts
0x479dd2a9…a74f
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 0x767c56c7b2…9aec85
Audit this contract →
← previous block·next block →recent activity