← previous blocknext block →recent activity
Analyzing
Block #95,624,484
19 transactions · 18 stateful · 2026-08-13 11:54:28 UTC
Parallelism
89/100
Blocked
17%
Avg conflicts / tx
0.16
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #95,624,484 · 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
1w02w13w04w16w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc0cd9fc1…1c44
0x34b655…2a6f
4 touches
1 conflict
0xe74deb99…9e5b
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0031
0x59df86…2780
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x3f2796bf…f0fa
0x34b655…2a6f
4 touches
1 conflict
0xc09c3422…3c8b
0x34b655…2a6f
4 touches
1 conflict
0x8b2c44b4…7e59
0x2b46c0…1669
2 touches
0 conflicts
0x915c095e…c1e5
0x2b46c0…1669
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 0xc0cd9fc147…b21c44
Audit this contract →
← previous block·next block →recent activity