← previous blocknext block →recent activity
Analyzing
Block #93,446,943
21 transactions · 20 stateful · 2026-08-05 20:50:51 UTC
Parallelism
90/100
Blocked
20%
Avg conflicts / tx
0.19
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #93,446,943 · 21 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
1w02w14w05w17w010w013w115w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6bc8f55b…7d11
0x34b655…2a6f
4 touches
1 conflict
0xb4e0a934…5fc7
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0xdfc21d7c…e062
0x34b655…2a6f
4 touches
1 conflict
0xd3d2b624…594f
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0x010f694c…2ed6
0x34b655…2a6f
4 touches
1 conflict
0x0c09832d…59b5
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 0x6bc8f55b1d…887d11
Audit this contract →
← previous block·next block →recent activity