← previous blocknext block →recent activity
Analyzing
Block #74,182,806
8 transactions · 7 stateful · 2026-05-12 21:14:03 UTC
Parallelism
75/100
Blocked
29%
Avg conflicts / tx
0.25
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #74,182,806 · 8 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
1w03w16w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x765c236f…ff45
0x2a68ba…90c5
4 touches
1 conflict
0x3bdab090…c5bf
0x34b655…2a6f
4 touches
1 conflict
0x768cffcd…2648
0x34b655…2a6f
4 touches
1 conflict
0xa75f9ff4…c3ef
0x34b655…2a6f
4 touches
1 conflict
0x5e3bee3f…bc74
0x065c9d…c394
3 touches
1 conflict
0x8e66da19…66b6
0x065c9d…c394
2 touches
0 conflicts
0xecd0ecca…82d5
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity