← previous blocknext block →recent activity
Analyzing
Block #105,634,563
19 transactions · 18 stateful · 2026-09-17 14:55:20 UTC
Parallelism
89/100
Blocked
28%
Avg conflicts / tx
0.26
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #105,634,563 · 19 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
2w03w14w05w010w011w113w117w118w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xb5f5f775…010b
0x34b655…2a6f
4 touches
1 conflict
0xbb2315b8…3574
0x34b655…2a6f
4 touches
1 conflict
0xcf17589f…048c
0x34b655…2a6f
4 touches
1 conflict
0x1668042d…2ef4
0x34b655…2a6f
4 touches
1 conflict
0x3230413b…bc7f
0x34b655…2a6f
4 touches
1 conflict
0xf346808d…6ad4
0x34b655…2a6f
4 touches
1 conflict
0x32d01f30…732f
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
1 conflict on slot 0xac2a02739b…81721b
Audit this contract →
← previous block·next block →recent activity