← previous blocknext block →recent activity
Analyzing
Block #92,860,865
13 transactions · 13 stateful · 2026-08-03 19:42:04 UTC
Parallelism
85/100
Blocked
23%
Avg conflicts / tx
0.23
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #92,860,865 · 13 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
1w02w14w05w17w08w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x42e917f7…ed8c
0x34b655…2a6f
4 touches
1 conflict
0x77722039…2e5c
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0x12116623…41fd
0xd32edf…ff58
3 touches
1 conflict
0x38e870cb…4dfb
0x065c9d…c394
2 touches
0 conflicts
0x80afd9d9…57cf
0x065c9d…c394
2 touches
0 conflicts
0x828a0a23…5d36
0x065c9d…c394
2 touches
0 conflicts
0x93cd8311…e2a3
0x065c9d…c394
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 0x42e917f7fa…e0ed8c
Audit this contract →
← previous block·next block →recent activity