← previous blocknext block →recent activity
Analyzing
Block #101,665,373
6 transactions · 6 stateful · 2026-09-03 16:44:11 UTC
Parallelism
67/100
Blocked
17%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #101,665,373 · 6 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
1w02w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xeb1b66a1…ce4e
0x34b655…2a6f
4 touches
1 conflict
0xba149d38…48fe
0x34b655…2a6f
4 touches
1 conflict
0xbb9ab337…f4ec
0x34b655…2a6f
4 touches
1 conflict
0xcb10192b…9066
0x34b655…2a6f
4 touches
1 conflict
0xddf10453…d774
0x34b655…2a6f
4 touches
1 conflict
0xe8f860c0…35c9
0x34b655…2a6f
4 touches
1 conflict
0x3027f5b0…7a3f
0x34b655…2a6f
4 touches
1 conflict
0x4c15b948…d02e
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 0xeb1b66a1ed…55ce4e
Audit this contract →
← previous block·next block →recent activity