← previous blocknext block →recent activity
Analyzing
Block #101,988,384
56 transactions · 53 stateful · 2026-09-04 19:53:02 UTC
Parallelism
89/100
Blocked
19%
Avg conflicts / tx
0.23
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #101,988,384 · 56 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w27w08w110w113w214w351w353w354w455w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf4e1756d…1f63
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x2aa7be4c…0f84
0x34b655…2a6f
4 touches
1 conflict
0x34e61077…195a
0x34b655…2a6f
4 touches
1 conflict
0x51fc8795…126f
0x34b655…2a6f
4 touches
1 conflict
0x5c7b5ec0…0764
0x34b655…2a6f
4 touches
1 conflict
0x6823c28e…594c
0x34b655…2a6f
4 touches
1 conflict
0x6c7c1a4b…5751
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
3 conflicts on slot 0xf4e1756db6…981f63
Audit this contract →
← previous block·next block →recent activity