← previous blocknext block →recent activity
Analyzing
Block #101,491,871
18 transactions · 16 stateful · 2026-09-03 02:11:21 UTC
Parallelism
89/100
Blocked
19%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #101,491,871 · 18 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
2w03w14w05w16w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x21e8ab54…3b4b
0x34b655…2a6f
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x912b9be8…d714
0xd32edf…ff58
3 touches
1 conflict
0x0179e71d…e168
0x34b655…2a6f
2 touches
0 conflicts
0x0abd58f2…77a4
0x34b655…2a6f
2 touches
0 conflicts
0x11db128b…1153
0x34b655…2a6f
2 touches
0 conflicts
0x4d2851e7…6633
0x34b655…2a6f
2 touches
0 conflicts
0x55761e30…06fd
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 0x21e8ab549c…8c3b4b
Audit this contract →
← previous block·next block →recent activity