← previous blocknext block →recent activity
Analyzing
Block #108,498,753
23 transactions · 21 stateful · 2026-09-27 15:17:01 UTC
Parallelism
70/100
Blocked
48%
Avg conflicts / tx
0.83
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #108,498,753 · 23 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w08w09w110w211w312w413w414w515w617w118w221w022w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6302c76f…a5d2
0x34b655…2a6f
8 touches
6 conflicts
0x49890ced…6f23
0x34b655…2a6f
6 touches
3 conflicts
0x42522e76…2592
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x19dcf812…44d9
0x34b655…2a6f
4 touches
1 conflict
0x221e8974…2a9a
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0xa616a7aa…5135
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
6 conflicts on slot 0x6302c76fac…53a5d2
Audit this contract →
← previous block·next block →recent activity