← previous blocknext block →recent activity
Analyzing
Block #101,895,897
23 transactions · 22 stateful · 2026-09-04 12:03:55 UTC
Parallelism
65/100
Blocked
41%
Avg conflicts / tx
0.61
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #101,895,897 · 23 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w26w311w413w515w617w721w422w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3a1711ab…1ee8
0x34b655…2a6f
8 touches
6 conflicts
0x082a85db…aade
0x34b655…2a6f
6 touches
3 conflicts
0x2aa7be4c…0f84
0x34b655…2a6f
6 touches
3 conflicts
0x3380282c…cf3c
0x34b655…2a6f
6 touches
3 conflicts
0x477cb4f5…11b4
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x51fc8795…126f
0x34b655…2a6f
6 touches
3 conflicts
0x56e0d685…c960
0x34b655…2a6f
6 touches
3 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
6 conflicts on slot 0x3a1711ab90…521ee8
Audit this contract →
← previous block·next block →recent activity