← previous blocknext block →recent activity
Analyzing
Block #93,354,082
18 transactions · 15 stateful · 2026-08-05 13:03:59 UTC
Parallelism
89/100
Blocked
20%
Avg conflicts / tx
0.22
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #93,354,082 · 18 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
2w05w06w18w010w113w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd8bc53a3…c2fe
0x34b655…2a6f
4 touches
1 conflict
0x21898044…a071
0x065c9d…c394
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x74fd0a9b…3aaa
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0xd55ca13c…3eb2
0x34b655…2a6f
4 touches
1 conflict
0x67f3716d…ebb4
0x065c9d…c394
3 touches
1 conflict
0x62e20208…be65
0x0555e3…2b9c
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 0xd8bc53a346…42c2fe
Audit this contract →
← previous block·next block →recent activity