← previous blocknext block →recent activity
Analyzing
Block #101,854,832
14 transactions · 12 stateful · 2026-09-04 08:37:08 UTC
Parallelism
79/100
Blocked
25%
Avg conflicts / tx
0.36
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #101,854,832 · 14 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w05w17w09w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x165d6ec5…b2d2
0x34b655…2a6f
4 touches
1 conflict
0x7c93b38a…9e69
0x34b655…2a6f
4 touches
1 conflict
0xea06b19c…b3c8
0x34b655…2a6f
4 touches
1 conflict
0x99449f41…9d5d
0x34b655…2a6f
4 touches
1 conflict
0xb3fb9fb5…64db
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x2bd1c200…56de
0x34b655…2a6f
4 touches
1 conflict
0xae7853a9…4e05
0x34b655…2a6f
3 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 0x165d6ec5bf…f1b2d2
Audit this contract →
← previous block·next block →recent activity