← previous blocknext block →recent activity
Analyzing
Block #117,305,534
20 transactions · 18 stateful · 2026-10-28 10:44:02 UTC
Parallelism
80/100
Blocked
22%
Avg conflicts / tx
0.25
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #117,305,534 · 20 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
9w010w114w015w118w219w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfd808de1…5c3c
0x34b655…2a6f
6 touches
3 conflicts
0x58f586c0…f3a8
0x34b655…2a6f
4 touches
1 conflict
0x65bc7678…5518
0x34b655…2a6f
4 touches
1 conflict
0x364fbde6…1520
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xf5dc501b…831c
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0xcb45d9d6…cb85
0x1b6862…e19c
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
3 conflicts on slot 0xfd808de135…295c3c
Audit this contract →
← previous block·next block →recent activity